Installing Airbrake in a Python application

We’re sick of bad software. Airbrake’s goal is to help developers produce better software faster so that we can get back to enjoying technology. Any python error or panic can be sent to the Airbrake dashboard using Pybrake SDK. The library is very small and has very little overhead.

Key Features

  • Simple to install and configure
  • Python Error Detection with Full Stack Traces
  • Monitoring Python’s performance such as HTTP route statistics, SQL queries, and Job execution statistics.
  • Filtering Python Errors, severity and control notification thresholds.
  • Add extra context to errors before they are sent
  • Integrates with your existing logger
  • Asynchronous reporting
  • Resends the Error notice or Performance data if the Airbrake Server malfunctions. Several configurations must be made as shown below. (Have a question? Look here at FAQ)
  • Support for environments

Supported Frameworks

Pybrake provides a ready-to-use solution with minimal configuration for python frameworks.


















Installation & Configuration

What version of Python are you using?

The version of Python your app is using determines which installation instructions to follow.

The pybrake notifier supports Python 3.6 and above.

pip install -U pybrake


To add Pybrake to your application project_id & project_key are required, to find it browse to your project’s Settings and copy the data from the right sidebar of the Airbrake portal.

import pybrake

notifier = pybrake.Notifier(project_id=123,

Additional Settings

List of Parameter Notifier will expect

Configuration parameter which can configure different functionality by Notifier

Parameter NameTypeDescriptionRequiredDefault Value
project_idIntInteger Airbrake project id from Airbrake.ioYes
project_keyStringSecret key of Airbrake project in string format from Airbrake.ioYes
performance_statsBooleanEnable/disable performance monitoring if False, pybrake will not send any monitoring stats to Which include (route, query, & queue).NoTrue
query_statsBooleanEnable/disable query stats monitoring if False, pybrake will not send query monitoring stats to
queue_statsBooleanEnable/disable queue stats monitoring if False, pybrake will not send queue monitoring stats to
max_queue_sizeIntMaximum number for thread pool queue sizeNo1000
max_workersIntMaximum number of thread pool can make by NotifierNonumber CPU count * 5
root_directoryStringRoot directory path of project to finf git directoryNoPROJECT_DIR
environmentStringProject running environment, Like: development, testing, production. Can make own environment.Noproduction
keys_blocklistListTo transmit an airbrake on an error notification, a list of sensitive parameter’s information must be blocked or filterout.No[re.compile(“password”), re.compile(“secret”)]
remote_configBooleanConfigure pybrake using, a remote server. If True, pybrake will ignore any configutation done during the initialization of the notifier.NoFalse
backlog_enabledBooleanIf backlog_enabled is set as true then pybrake will manage failed performance stats and errors and periodically sends them asynchronously in the background (every 1 minute). Default value: FalseNoFalse
max_backlog_sizeIntSet up the length of failed stats backlog queue. Default value: 100. Up to 100 backlog items for errors and 100 backlog items for performance stats (Shared with Routes, Route breakdown, query, queue stats). In the event that the backlog queue becomes full, the item will be replaced and an error will be recorded.No100

Error Monitoring

Sending errors to Airbrake

    raise ValueError('hello')
except Exception as err:

Sending errors synchronously

The notify function communicates errors asynchronously via ThreadPoolExecutor and produces a concurrent.futures.Future by default; however, the notify_sync function provides a synchronous API

notice = notifier.notify_sync(err)
if 'id' in notice:

Adding custom params

You can design and send an error notification in two phases to set custom parameters

notice = notifier.build_notice(err)
notice['params']['myparam'] = 'myvalue'

# Asynchronously

# Synchronously

You can also use the add_filter function to add custom params to every error notice before it’s sent to Airbrake instead of sending it manually

def my_filter(notice):
    notice['params']['myparam'] = 'myvalue'
    return notice


Linking errors to routes

You can link error notices with the routes by setting the route e.g. /hello and httpMethod e.g. GET, POST in the custom parameters for error notices. For example:

notice = notifier.build_notice(err)
notice['context']["route"] = "route-name"
notice['context']["httpMethod"] = "http-method-name"

Set severity

Severity allows categorizing how severe an error is. By default, it’s set to error. To redefine severity, simply overwrite context/severity of a notice object. For example:

notice = notifier.build_notice(err)
notice['params']['myparam'] = 'myvalue'
notice['context']["severity"] = "critical"

# Asynchronously

# Synchronously

Ignoring notices

You can use the add_filter function to disregard any notifications or faults that are issued in your application that you don’t want to submit to Airbrake

def my_filter(notice):
    if notice['context']['environment'] == 'development':
        # Ignore notices in development environment.
        return None
    return notice


Filtering/Blocking keys data

You can specify a list of keys containing sensitive information that must be filtered out using the keys_blocklist option

notifier = pybrake.Notifier(
        'password',           # exact match
        re.compile('secret'), # regexp match

Logging integration

Pybrake has a logging handler that transmits all of your logs to Airbrake

import logging
import pybrake

airbrake_handler = pybrake.LoggingHandler(notifier=notifier,

logger = logging.getLogger('test')

logger.error('something bad happened')

Disabling pybrake logs

Setting the logging level to logging.CRITICAL will mute the pybrake logger.

import logging


Performance Monitoring

You can read more about our Performance Monitoring offering in our docs.

Sending route stats

The function notifier.routes.notify allows you to transmit route statistics to Airbrake. Below listed frameworks are supported by the library for now. (Your routes are automatically monitored.) This API can also be used manually.:

from pybrake import RouteMetric

metric = RouteMetric(method=request.method, route=route)
metric.status_code = response.status_code
metric.content_type = response.headers.get("Content-Type")
metric.end_time = time.time()


Sending route breakdowns

Airbrake can get performance breakdown stats through the notifier.routes.breakdowns.notify command. This API can be used manually:

from pybrake import RouteMetric

metric = RouteMetric(
metric._groups = {'db': 12.34, 'view': 56.78}


Sending query stats

The function notifier.queries.notify allows you to transmit SQL query statistics to Airbrake. The library integrates with below listed frameworks (your requests are automatically recorded).

Using SQLAlchemy
Using Django ORM
Using Masonite ORM

This API can also be used manually:

    query="SELECT * FROM foos",

Sending queue stats

The function notifier.queues.notify allows you to submit queue (task) statistics to Airbrake. Celery & Masonite are both integrated with the library, so your queues are automatically tracked. This API can also be used manually:

from pybrake import QueueMetric

metric = QueueMetric(queue="foo_queue")
metric._groups = {'redis': 24.0, 'sql': 0.4}


Exception limit

The maximum size of an exception is 64KB. Exceptions that exceed this limit will be truncated to fit the size.

Taking Pybrake further

Now that you have configured Airbrake to report exceptions from your Python 3 and above app, we recommend you add extra context to your errors and add Airbrake to your existing logger. Please visit the Pybrake GitHub repo for the full list of notifier features.