python 记录到数据库
我正在寻找一种方法,让 python 记录器模块记录到数据库,并在数据库关闭时回退到文件系统。
所以基本上有两件事:如何让记录器记录到数据库以及如何在数据库关闭时使其落入文件日志记录。
I'm seeking a way to let the python logger module to log to database and falls back to file system when the db is down.
So basically 2 things: How to let the logger log to database and how to make it fall to file logging when the db is down.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
我最近设法用 Python 编写了自己的数据库记录器。由于我找不到任何示例,我想我将我的示例发布在这里。与 MS SQL 一起使用。
数据库表可能如下所示:
类本身:
和用法示例:
上面将记录到数据库和文件。如果不需要文件 - 跳过“logging.basicConfig(filename=log_file_path)”行。使用“log”记录的所有内容 - 将被记录为 MY_LOGGER。如果出现一些外部错误(即在导入的模块或其他错误中) - 错误将显示为“root”,因为“root”记录器也处于活动状态,并且正在使用数据库处理程序。
I recently managed to write my own database logger in Python. Since I couldn't find any example I thought I post mine here. Works with MS SQL.
Database table could look like this:
The class itself:
And usage example:
Above will log both to the database and to the file. If file is not needed - skip the 'logging.basicConfig(filename=log_file_path)' line. Everything logged using 'log' - will be logged as MY_LOGGER. If some external error appears (i.e. in the module imported or something) - error will appear as 'root', since 'root' logger is also active, and is using the database handler.
自己编写一个处理程序,将日志定向到有问题的数据库。当失败时,您可以将其从记录器的处理程序列表中删除。有很多方法可以处理故障模式。
Write yourself a handler that directs the logs to the database in question. When it fails, you can remove it from the handler list of the logger. There are many ways to deal with the failure-modes.
使用备份记录器将 Python 记录到数据库
问题
当我在服务器内运行 Django 项目时,我遇到了同样的问题,因为有时您需要远程检查日志。
解决方案
首先,记录器需要一个处理程序来将日志插入数据库。在此之前,由于我的SQL不好,需要一个ORM,我选择SQLAlchemy。
模型:
这是插入数据库的 CRUD:
处理程序:
测试以检查记录器:
您可以看到处理程序接受一个备份记录器,当数据库插入失败时可以使用它。
一个很好的改进是通过线程登录数据库。
Python logging to a database with a backup logger
Problem
I had the same problem when I ran a Django project inside the server since sometimes you need to check the logs remotely.
Solution
First, there is a need for a handler for the logger to insert logs in to the database. Before that and since my SQL is not good, an ORM is needed that I choose SQLAlchemy.
model:
This is the crud for insertion into the database:
The handler:
Test to check the logger:
You can see the handler accepts a backup logger that can use it when the database insertion fails.
A good improvement can be logging into the database by threading.
我又把这个挖出来了
SqlAlchemy 有一个解决方案(此配方不需要 Pyramid):
https://docs.pylonsproject.org/projects/pyramid-cookbook/en/latest/logging/sqlalchemy_logger.html
您可以通过添加额外的字段来改进日志记录,这是一个指南: https://stackoverflow.com/a/17558764/1115187
回退到 FS
不确定这是不是100% 正确,但您可以有 2 个处理程序:
只需用
try- except
包装 DB 提交即可。但请注意:该文件将包含所有日志条目,而不仅仅是数据库保存失败的条目。I am digging this out again.
There is a solution with SqlAlchemy (Pyramid is NOT required for this recipe):
https://docs.pylonsproject.org/projects/pyramid-cookbook/en/latest/logging/sqlalchemy_logger.html
And you could improve logging by adding extra fields, here is a guide: https://stackoverflow.com/a/17558764/1115187
Fallback to FS
Not sure that this is 100% correct, but you could have 2 handlers:
Just wrap the DB-commit with a
try-except
. But be aware: the file will contain ALL log entries, but not only entries for which DB saving was failed.老问题,但为其他人放弃这个问题。如果你想使用 python 日志记录,你可以添加两个处理程序。一个用于写入文件,一个旋转文件处理程序。这是稳健的,并且无论 dB 是否上升都可以完成。
另一个可以写入另一个服务/模块,例如 pymongo 集成。
查找logging.config,了解如何从代码或json 设置处理程序。
Old question, but dropping this for others. If you want to use python logging, you can add two handlers. One for writing to file, a rotating file handler. This is robust, and can be done regardless if the dB is up or not.
The other one can write to another service/module, like a pymongo integration.
Look up logging.config on how to setup your handlers from code or json.