test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added info about using logging to the 'Error reporting' howto. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14573 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Luke Plant 2010-11-16 14:00:38 +00:00
parent 165f13dc88
commit b9e6db4ae8
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/howto/error-reporting.txt
View File

@ -39,6 +39,14 @@ address, modify the :setting:`SERVER_EMAIL` setting.
To disable this behavior, just remove all entries from the :setting:`ADMINS` To disable this behavior, just remove all entries from the :setting:`ADMINS`
setting. setting.
.. seealso::
.. versionadded:: 1.3
Server error e-mails are sent using the logging framework, so you can
customize this behaviour by :doc:`customizing your logging configuration
</topics/logging>`.
404 errors 404 errors
---------- ----------
@ -76,3 +84,12 @@ The best way to disable this behavior is to set
:ref:`exception middleware <exception-middleware>`. If you do write custom :ref:`exception middleware <exception-middleware>`. If you do write custom
error handling, it's a good idea to emulate Django's built-in error handling error handling, it's a good idea to emulate Django's built-in error handling
and only report/log errors if :setting:`DEBUG` is ``False``. and only report/log errors if :setting:`DEBUG` is ``False``.
.. seealso::
.. versionadded:: 1.3
404 errors are logged using the logging framework. By default, these log
records are ignored, but you can use them for error reporting by writing a
handler and :doc:`configuring logging </topics/logging>` appropriately.