blocks|key|1491549|text|显然James是正确的，但是如果您想在数据存储中记录异常，有一些开源解决方案已经可用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1491550|1)+http://code.google.com/p/django-crashlog/：CrashLog是个不错的选择|offset|length|1491551|2)数据库日志也是一个很好的选择：http://code.google.com/p/django-db-log/|1491552|两者之间的区别是什么？我几乎看不到任何东西，所以任何一个都足够了。|1491553|我已经使用了这两种方法，它们都工作得很好。|1491554|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/django-crashlog/|1|http://code.google.com/p/django-db-log/^0|0|3|15|0|0|H|13|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

Obviously James is correct, but if you wanted to log exceptions in a datastore, there are a few open source solutions already available:

1) CrashLog is a good choice: <a href="http://code.google.com/p/django-crashlog/" rel="nofollow noreferrer">http://code.google.com/p/django-crashlog/</a>

2) Db-Log is a good choice as well: <a href="http://code.google.com/p/django-db-log/" rel="nofollow noreferrer">http://code.google.com/p/django-db-log/</a>

What is the difference between the two? Almost nothing that I can see, so either one will suffice.

I've used both and they work well.

blocks|key|1706659|text|在另一个答案中提到的django-db-log已被替换为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1706660|https://github.com/dcramer/django-sentry|offset|length|1706661|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|14|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

django-db-log, mentioned in another answer, has been replaced with:

<a href="https://github.com/dcramer/django-sentry" rel="noreferrer">https://github.com/dcramer/django-sentry</a>

blocks|key|1491671|text|正如已经提到的，Django+Sentry是一个很好的选择，但要正确地设置它(作为一个单独的网站)，需要做一些工作。如果您只想将所有内容记录到一个简单的文本文件中，下面是要放入settings.py中的日志配置|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1491672|LOGGING+=+{
++++'version':+1,
++++'disable_existing_loggers':+False,
++++'handlers':+{
++++++++#+Include+the+default+Django+email+handler+for+errors
++++++++#+This+is+what+you'd+get+without+configuring+logging+at+all.
++++++++'mail_admins':+{
++++++++++++'class':+'django.utils.log.AdminEmailHandler',
++++++++++++'level':+'ERROR',
+++++++++++++#+But+the+emails+are+plain+text+by+default+-+HTML+is+nicer
++++++++++++'include_html':+True,
++++++++},
++++++++#+Log+to+a+text+file+that+can+be+rotated+by+logrotate
++++++++'logfile':+{
++++++++++++'class':+'logging.handlers.WatchedFileHandler',
++++++++++++'filename':+'/var/log/django/myapp.log'
++++++++},
++++},
++++'loggers':+{
++++++++#+Again,+default+Django+configuration+to+email+unhandled+exceptions
++++++++'django.request':+{
++++++++++++'handlers':+['mail_admins'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+True,
++++++++},
++++++++#+Might+as+well+log+any+errors+anywhere+else+in+Django
++++++++'django':+{
++++++++++++'handlers':+['logfile'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+False,
++++++++},
++++++++#+Your+own+app+-+this+assumes+all+your+logger+names+start+with+"myapp."
++++++++'myapp':+{
++++++++++++'handlers':+['logfile'],
++++++++++++'level':+'WARNING',+#+Or+maybe+INFO+or+DEBUG
++++++++++++'propagate':+False
++++++++},
++++},
}|code-block|syntax|javascript|1491673|entityMap^0|2G|B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Django Sentry is a good way to go, as already mentioned, but there is a bit of work involved in setting it up properly (as a separate website). If you just want to log everything to a simple text file here's the logging configuration to put in your <code>settings.py</code>

<pre><code>LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'handlers': {
 # Include the default Django email handler for errors
 # This is what you'd get without configuring logging at all.
 'mail_admins': {
 'class': 'django.utils.log.AdminEmailHandler',
 'level': 'ERROR',
 # But the emails are plain text by default - HTML is nicer
 'include_html': True,
 },
 # Log to a text file that can be rotated by logrotate
 'logfile': {
 'class': 'logging.handlers.WatchedFileHandler',
 'filename': '/var/log/django/myapp.log'
 },
 },
 'loggers': {
 # Again, default Django configuration to email unhandled exceptions
 'django.request': {
 'handlers': ['mail_admins'],
 'level': 'ERROR',
 'propagate': True,
 },
 # Might as well log any errors anywhere else in Django
 'django': {
 'handlers': ['logfile'],
 'level': 'ERROR',
 'propagate': False,
 },
 # Your own app - this assumes all your logger names start with "myapp."
 'myapp': {
 'handlers': ['logfile'],
 'level': 'WARNING', # Or maybe INFO or DEBUG
 'propagate': False
 },
 },
}
</code></pre>

blocks|key|1706798|text|自从EMP提交最有用的代码以来，已经过去了一段时间。我刚刚实现了它，当我在一些manage.py选项上翻来覆去，试图找出一个错误时，我得到了一个弃用警告，大意是在我当前版本的Django+(1.5？)mail_admins处理程序现在需要一个require_debug_false过滤器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1706799|以下是修改后的代码：|1706800|LOGGING+=+{
++++'version':+1,
++++'disable_existing_loggers':+False,
++++'filters':+{
+++++++++'require_debug_false':+{
+++++++++++++'()':+'django.utils.log.RequireDebugFalse'
+++++++++}
+++++},
++++'handlers':+{
++++++++#+Include+the+default+Django+email+handler+for+errors
++++++++#+This+is+what+you'd+get+without+configuring+logging+at+all.
++++++++'mail_admins':+{
++++++++++++'class':+'django.utils.log.AdminEmailHandler',
++++++++++++'level':+'ERROR',
++++++++++++'filters':+['require_debug_false'],
+++++++++++++#+But+the+emails+are+plain+text+by+default+-+HTML+is+nicer
++++++++++++'include_html':+True,
++++++++},
++++++++#+Log+to+a+text+file+that+can+be+rotated+by+logrotate
++++++++'logfile':+{
++++++++++++'class':+'logging.handlers.WatchedFileHandler',
++++++++++++'filename':+'/home/username/public_html/djangoprojectname/logfilename.log'
++++++++},
++++},
++++'loggers':+{
++++++++#+Again,+default+Django+configuration+to+email+unhandled+exceptions
++++++++'django.request':+{
++++++++++++'handlers':+['mail_admins'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+True,
++++++++},
++++++++#+Might+as+well+log+any+errors+anywhere+else+in+Django
++++++++'django':+{
++++++++++++'handlers':+['logfile'],
++++++++++++'level':+'ERROR',
++++++++++++'propagate':+False,
++++++++},
++++++++#+Your+own+app+-+this+assumes+all+your+logger+names+start+with+"myapp."
++++++++'myapp':+{
++++++++++++'handlers':+['logfile'],
++++++++++++'level':+'DEBUG',+#+Or+maybe+INFO+or+WARNING
++++++++++++'propagate':+False
++++++++},
++++},
}|code-block|syntax|javascript|1706801|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Some time has passed since EMP's most helpful code submission. I just now implemented it, and while thrashing around with some manage.py option, to try to chase down a bug, I got a deprecation warning to the effect that with my current version of Django (1.5.?) a require_debug_false filter is now needed for the mail_admins handler.

Here is the revised code:

<pre><code>LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'filters': {
 'require_debug_false': {
 '()': 'django.utils.log.RequireDebugFalse'
 }
 },
 'handlers': {
 # Include the default Django email handler for errors
 # This is what you'd get without configuring logging at all.
 'mail_admins': {
 'class': 'django.utils.log.AdminEmailHandler',
 'level': 'ERROR',
 'filters': ['require_debug_false'],
 # But the emails are plain text by default - HTML is nicer
 'include_html': True,
 },
 # Log to a text file that can be rotated by logrotate
 'logfile': {
 'class': 'logging.handlers.WatchedFileHandler',
 'filename': '/home/username/public_html/djangoprojectname/logfilename.log'
 },
 },
 'loggers': {
 # Again, default Django configuration to email unhandled exceptions
 'django.request': {
 'handlers': ['mail_admins'],
 'level': 'ERROR',
 'propagate': True,
 },
 # Might as well log any errors anywhere else in Django
 'django': {
 'handlers': ['logfile'],
 'level': 'ERROR',
 'propagate': False,
 },
 # Your own app - this assumes all your logger names start with "myapp."
 'myapp': {
 'handlers': ['logfile'],
 'level': 'DEBUG', # Or maybe INFO or WARNING
 'propagate': False
 },
 },
}
</code></pre>

blocks|key|1706849|text|我的fcgi脚本出现了一个恼人的问题。它甚至在django开始之前就发生了。缺少日志记录实在是太痛苦了。无论如何，将stderr重定向到一个文件作为第一件事很有帮助：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1706850|#!/home/user/env/bin/python
sys.stderr+=+open('/home/user/fcgi_errors',+'a')|code-block|syntax|javascript|1706851|entityMap^0|2|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I just had an annoying problem with my <code>fcgi</code> script. It occurred before django even started. The lack of logging is sooo painful. Anyway, redirecting stderr to a file as the very first thing helped a lot:

<pre><code>#!/home/user/env/bin/python
sys.stderr = open('/home/user/fcgi_errors', 'a')
</code></pre>

So, when playing with the development I can just set <code>settings.DEBUG</code> to <code>True</code> and if an error occures I can see it nicely formatted, with good stack trace and request information.

But on kind of production site I'd rather use <code>DEBUG=False</code> and show visitors some standard error 500 page with information that I'm working on fixing this bug at this moment ;) 
At the same time I'd like to have some way of logging all those information (stack trace and request info) to a file on my server - so I can just output it to my console and watch errors scroll, email the log to me every hour or something like this.

What logging solutions would you recomend for a django-site, that would meet those simple requirements? I have the application running as <code>fcgi</code> server and I'm using apache web server as frontend (although thinking of going to lighttpd).

How do you log server errors on django sites

数据存储

数据库

服务器

Django

因此，在进行开发时，我只需将settings.DEBUG设置为True，如果发生错误，我可以看到它的格式很好，具有良好的堆栈跟踪和请求信息。但在某种生产站点上，我更愿意使用DEBUG=False，并向访问者显示一些标准的错误500页面，其中包含我目前正在修复的这个bug的信息;)同时，我希望有一些方法可以将所有这些信息...

问如何在django站点上记录服务器错误
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在django站点上记录服务器错误EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在django站点上记录服务器错误
EN