skip to navigation
skip to content

Not Logged In

django-shoogie 0.6b

Log server errors to database

Shoogie is a small django application with middleware that logs exceptions to a table in the database, along with django's standard HTML debug response. It is intended to be a lightweight alternative to django-sentry, inspired by this answer on stackoverflow.

The logging middleware doesn't do anything when running in DEBUG mode.

Shoogie has been used in production since March 2012.

The name Shoogie is a diminutive of the Hebrew word sh'giah (שגיאה), which means 'error.' It also happens to be the name of a popular kids' candy snack in Israel. It's our hope that django-shoogie will make dealing with server errors a sweeter experience.

Key Features

  • Simple, server-error specific logging
  • Logs django's familiar technical 500 response
  • Uses django's standard admin interface
  • Easy retrieval by user, exception, file, function
  • Easy extraction of users' email addresses
  • Middleware can easily be placed outside transaction management
  • Configurable exception ignores
  • Configurable traceback filtering


To install shoogie:

pip install django-shoogie

To use shoogie in a django project, add it to the INSTALLED_APPS and add the shoogie middleware to MIDDLEWARE_CLASSES in your Be sure to put the middleware above the transaction middleware, or errors which cause the DB transaction to be rolled back will not be logged. The django.contrib.admin app must also be installed to view the errors logged via django's admin interface:

        'shoogie.middleware.ExceptionLoggingMiddleware',        # <---
        # ...

    'shoogie',                      # <---
    # ...

Make sure to run syncdb after adding shoogie to create the shoogie_servererror table.


Shoogie can be configured with the following settings:


A sequence of absolute dotted paths of exceptions which it should not log. These exceptions and their subclasses will be ignored. The default value is:



A sequence of regular expression pairs (filename, funcname) used to filter the traceback included in django's debug page. This is intended to eliminate the time needed to render, store, and display traceback frames which aren't useful. The default value is:

    ('/django/core/handlers/$', '^get_response$'),
    ('/django/template/', 'render'),


Errors logged by shoogie can be viewed via django's admin interface at /admin/shoogie/servererror/.

To view the data fields stored in the log entry, click in the first column.

To visit the url in which the error occurred, click the 'path' column. This won't work if the host is inaccessible, if the request method was something other than GET, or if the path isn't really an HTTP request path (see below).

If a user is logged with an entry, a link to the admin detail page for the user will be displayed in the admin list.

Click the 'debug' link to view the django-generated 'technical response' (debug page) for the exception.

To get a list of users and email addresses who encountered a set of errors, select the log entries using the checkboxes on the left, then select "Get user email addresses for selected errors" from the 'Action' drop-down menu and click the 'Go' button.

To mark a set of errors as resolved or as not resolved, select the entries in question and pick the appropriate action from the drop-down as above.


Shoogie can also be used to log exceptions directly. This could be useful for exceptions occurring in back-end processes such as long-running calculations, cron-jobs, and celery workers:

from shoogie import logger
logger.log_exception([request, [exc_type, exc_val, tb]])

Logs an exception to the db. If exc_type, exc_val, and tb aren't supplied, they will be retrieved using sys.exc_info(). The django technical debug page stored will display the traceback as with errors occuring in normal views.

If request is given, whatever request information is present will also be saved in the log entry. request should be an object which implements, partially or wholly, the same interface as a django.http.HttpRequest.

As a convenience for logging exceptions outside the context of an HTTP request, log_exception can be passed a string instead, which will be logged as the request path. Make sure the logging is done outside any transaction which might be reversed by the exception being logged. A general pattern as follows is recommended:

    with transaction.commit_on_success():
        "insert your processing here"
File Type Py Version Uploaded on Size
django-shoogie-0.6b.tar.gz (md5) Source 2013-11-17 10KB
  • Downloads (All Versions):
  • 23 downloads in the last day
  • 40 downloads in the last week
  • 156 downloads in the last month