登录到数据库而不是日志文件 [英] Log to database instead of log files

问题描述

我有兴趣将所有 Rails 应用程序日志发送到数据库(MySQL 或 MongoDB)中，作为日志文件的补充或替代.有几个原因，其中大部分与日志文件分析有关.我们已经在使用 Google Analytics，但是我们想做的很多事情在 Analytics 中并不可行.

I'm interested in sending all Rails application logging to a database (MySQL or MongoDB) either in addition to or instead of to a log file. There are a few reasons, most of which are concerned about log file analysis. We already use Google Analytics, but there are a variety of things we want to do that aren't as workable in Analytics.

此外，我想通过查看日志对问题进行实时"调查.筛选日志文件是一种繁琐的方法，我希望进行比日志文件(轻松)允许的更好的搜索和过滤.

Furthermore, I'd like to do "real time" investigation of issues by looking at logs. Sifting through a log file is a tedious way to do that, and I'd like to do better searching and filtering than a log file (easily) allows for.

最后，我经常想检查一些更接近站点访问者行为的东西:例如，跟踪通过站点的路径，以便我可以看到用户在发生错误之前查看的最后一页是什么.鉴于我们有多个应用服务器，单独的日志文件让这变得非常痛苦.如果所有数据都在数据库中，那么我可以轻松查看给定访问者的正确页面顺序.我知道 Syslog 是解决这个特定问题(单个日志文件/存储库)的一种方法，但我想将它与我与数据库搜索相关联的更好的搜索能力结合起来.

Finally, I often want to examine something closer to site visitor behavior: tracing the path through the site for example, so that I can see what the last page was that a user was looking at before an error occurred. Given we have multiple app servers, the separate log files make this a real pain. If all the data were in a database, I could then easily see the proper sequence of pages for a given visitor. I know that Syslog would be one way to solve this particular thing (single log file/repository), but I want to combine that with better searching abilities that I associate with database searches.

我想知道人们推荐什么来解决这个问题.您是直接登录到数据库，还是将日志文件转储到数据库中(但是您的方法是什么，以便它基本上是实时的/与日志文件本身一样最新)?

I'm wondering what folks recommend to solve this. Do you directly log to a database, or do you dump log files into a DB (but what's your approach for that so that it's essentially realtime/as up to date as the logfile itself)?

我目前正在确定我想要这个日志记录的级别，因为我看到的另一件事是编写一个小的 Rack 过滤器来记录所有请求.这会错过正常 Rails 日志转储出来的所有额外输出(所有 SQL 和缓存命中和未命中的输出等)，但它会实现我的目标的很大一部分，并且似乎具有不打扰的优势系统中的任何其他内容.

I am currently determining at what level I'd like this logging, because another thing I looked at is writing a small Rack filter that would log all requests. This would miss all the extra output that the normal Rails logging dumps out (all the SQL and output on cache hits and misses, etc.), but it would achieve a big part of my goal, and seems to have the advantage of not disturbing anything else in the system.

无论如何，我不是在寻找一个正确的答案，更多的是关于其他人在同样的情况下可能会做什么的讨论和信息.

Anyway, I am not looking for one right answer, more of a discussion and information on what anyone else might be doing in this same light.

推荐答案

我的公司一直在将一些结构化的流量信息直接记录到 MySQL 日志数据库中.该数据库被下游复制到另一个数据库.所有分析都在最终的数据库复制之后运行.我们的网站维持着相当多的流量.到目前为止，它似乎没有任何大问题.但是，我们的 IT 部门对当前设置的可扩展性越来越担心，并建议我们将日志信息卸载到正确的"日志文件中.然后日志文件将重新插入到相同的下游数据库表中.这让我想到了这个问题.:)

My company have been logging some structured traffic info straight into a MySQL log database. This database is replicated downstream to another database. All analytics run off the final database replication. Our site sustain quite a bit of traffic. So far, it doesn't seem to have any major problems. However, our IT department have some growing concerns regarding to the scalability of the current setup and is suggesting that we offload the log info onto "proper" log-files. The log-files will then be reinserted back into the same downstream database tables. Which brings me to this question. :)

以下是我看到的关于日志文件与日志数据库(关系)主题的一些优缺点:

Here are some of pros and cons that I see regarding to the subject of log-files vs log-db (relational):

• 日志文件快速、可靠且可扩展(至少我听说雅虎大量使用日志文件进行点击跟踪分析).
• 日志文件易于系统管理员维护.
• 日志文件可以非常灵活，因为您几乎可以向其中写入任何内容.
• 日志文件需要大量解析，并且可能需要简化地图类型的数据提取设置.
• log-db 结构更接近您的应用程序，从而使某些功能的周转时间更短.这可能是一种祝福，也可能是一种诅咒.从长远来看，这可能是一种诅咒，因为您很可能最终会得到一个高度耦合的应用程序和分析代码库.
• log-db 可以减少日志记录噪音和冗余，因为日志文件仅在日志文件的位置插入，因为 log-db 使您能够进行更新和相关插入(如果你敢的话，可以进行标准化).
• 如果您使用数据库分区和/或多日志数据库(通过下游复制重新加入数据)，log-db 也可以快速且可扩展

我认为在我的情况下需要对日志数据库进行一些压力测试.这样至少我知道我有多少净空.

I think some stress tests on the log database are needed in my situation. This way at least I know how much headroom I have.

最近，我一直在研究一些基于键值/文档的数据库，例如 Redis、Tokyo Cabinet 和 MongoDB.这些快速插入的数据库可能是最佳选择，因为它们提供了不同程度的持久性、高(写入)吞吐量和查询功能.它们可以使数据提取过程比通过日志文件进行解析和减少映射简单得多.

Recently, I've been looking into some key-value / document-based databases like Redis, Tokyo Cabinet, and MongoDB. These fast inserting databases can potentially be the sweet spot since they provide persistence, high (write) throughputs, and querying capabilities to varying degrees. They can make the data-extraction process much simpler than parsing and map-reducing through gigs of log files.

从长远来看，我认为拥有强大的分析数据仓库至关重要.从分析数据中释放应用程序数据，反之亦然，这可能是一个巨大的胜利.

In the long run, I believe it is crucial to have a robust analytics data warehouse. Freeing application data from analytic data and vice versa can be a big WIN.

最后，我想指出 StackOverflow 上有许多类似/密切相关的问题，以防您想扩大讨论范围.

Lastly, I would just like to point out there are many similar / closely related questions here on StackOverflow in case you want to broaden your discussion.

• 存储多个日志文件
• 正在将服务器日志文件写入数据库是个好主意吗?
• 使用 SQL Server 进行应用程序日志记录.利弊?
• 在日志中快速搜索
• 用于日志记录的单独生产数据库
• 你登录到您的数据库，当您的数据库宕机时，您在哪里登录?

rsyslog 看起来很有趣.它使您能够直接写入 MySQL.如果您使用 Ruby，您应该查看日志记录 gem.它提供多目标日志记录功能.这太好了.

rsyslog looks very interesting. It gives you the ability to write directly to MySQL. If you are using Ruby, you should have a look at the logging gem. It provides multi-target logging capabilities. It's really nice.

这篇关于登录到数据库而不是日志文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！