Skip to content

Commit

Permalink
Added info about using logging to the 'Error reporting' howto.
Browse files Browse the repository at this point in the history
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14573 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
spookylukey committed Nov 16, 2010
1 parent 165f13d commit b9e6db4
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions docs/howto/error-reporting.txt
Original file line number Original file line Diff line number Diff line change
Expand Up @@ -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
---------- ----------


Expand Down Expand Up @@ -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.

0 comments on commit b9e6db4

Please sign in to comment.