Django 1.3 logging: 500 errors are not logged

Question

I'm struggling to make the 'django.request' logger work as advertised - 500 errors don't seem to propagate to handlers attached to it.

In the default logging configuration for every new project, the comment says the "logging performed by this configuration is to send an email to the site admins on every HTTP 500 error". Obviously the email is only sent if you've setup ADMINS correctly, but I'm not even seeing the handler get called when a view raises an exception.

I built a testcase starting with an empty project, and adding my own handler to the 'django.request' logger:

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'mail_admins': {
            'level': 'ERROR',
            'class': 'django.utils.log.AdminEmailHandler'
        },
        'my_error_handler' : {
            'level': 'ERROR',
            'class': 'log.MyErrorHandler'
        }
    },
    'loggers': {
        'django.request': {
            'handlers': ['mail_admins', 'my_error_handler'],
            'level': 'ERROR',
            'propagate': True,
        },
    }
}

The handler itself:

import logging
class MyErrorHandler(logging.Handler):     
    def emit(self, record):
        print "handling error: %s" % record

If I call .error() on the logger myself, everything works as it should. But when a 500 is generated by a view, neither of the handlers are called. My views.py:

import logging

def home(request):

    #this error will be processed by MyErrorHandler
    logging.getLogger('django.request').error("Custom error message")

    #this won't
    raise Exception('500 error message')

    return HttpResponse("Home")

Everything else is the project is default; DEBUG is True, the middleware config is unchanged. Is there some hidden config option I need to enable to have this work as it says in the docs?

Thanks, Matt.

Have you tried it with `DEBUG` set to `False`? When debugging don't the error handlers get overridden? — Steve Mayne, Jun 10 '11 at 10:47
Thank you Steve! Yes, django.core.handers.base.handle_uncaught_exception is the method which finally processes a view exception, and if settings.DEBUG it exits before calling logger.error. It seems like the logging docs should cover this - unless I've missed it somehow? — Matt, Jun 10 '11 at 11:57
I've added a proper answer so other people can find this information. I guessed this was the case because of the funky 'special' 500/404 pages Django displays when you're in debug mode - I don't think I ever read it in their (usually superb) docs. — Steve Mayne, Jun 10 '11 at 12:05

score 9 · Accepted Answer · answered Jun 10 '11 at 12:03

9

Try it with DEBUG set to False. When debugging is enabled, the error handlers in your settings.py get overridden.

answered Jun 10 '11 at 12:03

Steve Mayne

22,285
4
49
49

The problem with setting DEBUG to False is that the static files will not work (I am using Django to server static files in development). Is there any other workarounds to get the logging for 500 error to work while having DEBUG=True? Thanks. – tamakisquare Aug 30 '11 at 19:46

score 1 · Answer 2 · edited Oct 01 '12 at 02:41

1

Just for testing:

manage.py runserver --insecure

edited Oct 01 '12 at 02:41

andrewsi

10,807
132
35
51

answered Aug 02 '12 at 17:11

josx

15
5

1

To elaborate, this will force static files to be served even when `DEBUG = False` – Basic Apr 24 '13 at 11:29

Django 1.3 logging: 500 errors are not logged

2 Answers2

Linked