From b9e6db4ae801190cb2db188b8d5a5f0e891a6d56 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Tue, 16 Nov 2010 14:00:38 +0000 Subject: [PATCH] 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 --- docs/howto/error-reporting.txt | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/howto/error-reporting.txt b/docs/howto/error-reporting.txt index 9c61c97f658..baed78dcefd 100644 --- a/docs/howto/error-reporting.txt +++ b/docs/howto/error-reporting.txt @@ -39,6 +39,14 @@ address, modify the :setting:`SERVER_EMAIL` setting. To disable this behavior, just remove all entries from the :setting:`ADMINS` 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 + `. + 404 errors ---------- @@ -76,3 +84,12 @@ The best way to disable this behavior is to set :ref:`exception middleware `. If you do write custom 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``. + +.. 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 ` appropriately. +