Official bugsnag error monitoring and error reporting for django, flask, tornado and other python apps.
Clone or download
Cawllec v3.4.3 (#154)
* ci: Add Django 1.11, 2.0 and 2.1 to the build matrix

* fix(django): Update MIDDLEWARE to be compatible with Django 1.11+

* fix(django): Update ignore_classes for Django 1.11+

In my setup, by default, bugsnag logged some of Http404 despite the default config telling otherwise.

Looking at the examples, it was not super clear that I had to set the value to the full exception path in the setting. Then I managed to fix my setup by updating the exception path which I noticed was slightly different.

- Updating the examples to be clearer by specifying the full exception path
- Updating the default config to expect Http404 with full path or shortcut path

* Bump version

* ci: Add python 3.6 to build matrix

* next release: Bumped date
Latest commit 9ed1995 Aug 30, 2018

Bugsnag exception reporter for Python

Build status Documentation

The Bugsnag exception reporter for Python automatically detects and reports exceptions thrown your Django, WSGI, Tornado, Flask or plain Python app. Any uncaught exceptions will trigger a notification to be sent to your Bugsnag project. Learn more about monitoring and reporting Python errors with Bugsnag.


  • Automatically report unhandled exceptions and crashes
  • Report handled exceptions
  • Attach user information and custom diagnostic data to determine how many people are affected by a crash

Getting started

  1. Create a Bugsnag account
  2. Complete the instructions in the integration guide
  3. Report handled exceptions using bugsnag.notify()
  4. Customize your integration using the configuration options



All contributors are welcome! For information on how to build, test, and release, see our contributing guide.


The Bugsnag Python library is free software released under the MIT License. See LICENSE.txt for details.