Skip to main content

Log server errors to database

Project description


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.' *Shoogie* (שוגי) 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.

.. _this answer on stackoverflow:

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

Version Compatibility

django-shoogie is compatible with Django versions 1.3 to 1.6


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

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"

Related Projects

`django-sentry`_ is a large, very full-featured multi-platform error logging server,
which is based on django, and which offers prepackaged integration with
many other platforms. It offers some advanced features including aggregation of similar
exceptions, graphs, a fully web-2.0 real-time AJAX interface, and much more.

raven_ is the python logging client for django-sentry.

`django-erroneous`_ is a very simple logging system, similar in scope to
django-shoogie. It uses django signals rather than middleware to capture

`django-logdb`_ provides a handler for python's logging_ module which
stores log messages in the db. It includes middleware for exception logging.
It also provides aggregation and some of the features offered by django-sentry.

.. _django-sentry:
.. _raven:
.. _django-erroneous:
.. _django-logdb:
.. _logging:

Project details

Release history Release notifications

History Node


History Node


This version
History Node


History Node


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
django-shoogie-0.6.tar.gz (11.2 kB) Copy SHA256 hash SHA256 Source None Jun 5, 2014

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page