Integrating the SDK

Sentry captures data by using an SDK within your application’s runtime. These are platform specific and allow Sentry to have a deep understanding of how your application works.

Install our Python SDK using pip:

$ pip install --upgrade sentry-sdk

The SDK provides support for Python 2.7 and 3.4 or later. Integrations with specific frameworks (particularly asynchronous ones) may impose additional requirements though.

Migrating from Raven

If you are migrating from raven-python, have a look at our migration guide before continuing.

Connecting the SDK to Sentry

After you’ve completed setting up a project in Sentry, Sentry will give you a value which we call a DSN or Data Source Name. It looks a lot like a standard URL, but it’s just a representation of the configuration required by the Sentry SDKs. It consists of a few pieces, including the protocol, public key, the server address, and the project identifier.

Import and initialize the Sentry SDK early in your application’s setup:

import sentry_sdk

Verifying Your Setup

Great! Now that you’ve completed setting up the SDK, maybe you want to quickly test out how Sentry works. Start by capturing an exception:

sentry_sdk.capture_exception(Exception("This is an example of an error message."))

Once the exception is captured, you'll see the error in your Sentry dashboard.

Capturing Errors

In Python you can either capture a caught exception or the one currently held in sys.exc_info() by not passing an argument:

from sentry_sdk import capture_exception

except Exception as e:
    # Alternatively the argument can be omitted


A release is a version of your code that you deploy to an environment. When you give Sentry information about your releases, you unlock many new features:

  • Determine the issue and regressions introduced in a new release
  • Predict which commit caused an issue and who is likely responsible
  • Resolve issues by including the issue number in your commit message
  • Receive email notifications when your code gets deployed

After configuring your SDK, setting up releases is a 2-step process:

  1. Create Release and Associate Commits
  2. Tell Sentry When You Deploy a Release

For more information, see Releases Are Better With Commits.


Sentry supports additional context with events. Often this context is shared among any issue captured in its lifecycle, and includes the following components:

Structured Contexts
Structured contexts are typically set automatically.

Information about the current actor.

Key/value pairs which generate breakdown charts and search filters.

An event's severity.

A value used for grouping events into issues.

Unstructured Extra Data
Arbitrary unstructured data which the Sentry SDK stores with an event sample.

Setting Context

In addition to the structured context that Sentry understands, you can send arbitrary key/value pairs of data which the Sentry SDK will store alongside the event. These are not indexed, and the Sentry SDK uses them to add additional information about what might be happening.

.set_context() will take an object as the second argument and place the object inside contexts in the event payload.

from sentry_sdk import configure_scope

with configure_scope() as scope:
    scope.set_context("my_cool_data", {"foo": "bar"})

Extra Context

.set_extra() is similar to .set_context(), however it doesn't have reserved keys.

from sentry_sdk import configure_scope

with configure_scope() as scope:
    scope.set_extra("character_name", "Mighty Fighter")

Unsetting Context

Context is held in the current scope and thus is cleared out at the end of each operation — request, etc. You can also append and pop your own scopes to apply context data to a specific code block or function. Typically, unsetting context happens within an integration. For more information, see our Python integrations.

There are two different scopes for unsetting context — a global scope which Sentry does not discard at the end of an operation, and a scope that can be created by the user.

from sentry_sdk import configure_scope, push_scope, capture_exception

# This will be changed for all future events
with configure_scope() as scope:
    scope.user = some_user

with push_scope() as scope:
    # This will be changed only for the error caught inside and automatically discarded afterward
    scope.user = some_user

Capturing the User

Sending users to Sentry will unlock many features, primarily the ability to drill down into the number of users affecting an issue, as well as to get a broader sense about the quality of the application.

from sentry_sdk import configure_scope

with configure_scope() as scope:
    scope.user = {"email": ""}

Users consist of a few critical pieces of information which are used to construct a unique identity in Sentry. Each of these is optional, but one must be present for the Sentry SDK to capture the user:

Your internal identifier for the user.

The user's username. Generally used as a better label than the internal ID.

An alternative, or addition, to a username. Sentry is aware of email addresses and can show things like Gravatars, unlock messaging capabilities, and more.

The IP address of the user. If the user is unauthenticated, providing the IP address will suggest that this is unique to that IP. If available, we will attempt to pull this from the HTTP request data.

Additionally, you can provide arbitrary key/value pairs beyond the reserved names, and the Sentry SDK will store those with the user.

Tagging Events

Tags are key/value pairs assigned to events that can be used for breaking down issues or quick access to finding related events.

Most SDKs generally support configuring tags by configuring the scope:

from sentry_sdk import configure_scope

with configure_scope() as scope:
    scope.set_tag("page_locale", "de-at")

For more information, see the Tagging Events section in Context.

Setting the Level

You can set the severity of an event to one of five values: fatal, error, warning, info, and debug. error is the default, fatal is the most severe, and debug is the least severe.

from sentry_sdk import configure_scope

with configure_scope() as scope:
    scope.level = 'warning'

Setting the Fingerprint

Sentry uses a fingerprint to decide how to group errors into issues.

For some very advanced use cases, you can override the Sentry default grouping using the fingerprint attribute. In supported SDKs, this attribute can be passed with the event information and should be an array of strings.

If you wish to append information, thus making the grouping slightly less aggressive, you can do that as well by adding the special string {{default}} as one of the items.

For code samples, see the Grouping & Fingerprints page.

For more information, see Aggregate Errors with Custom Fingerprints.

Advanced Usage

Advanced Configuration

The Sentry SDK sets the options when you first initialize the SDK.

import sentry_sdk


For more information, see:

Sentry will automatically record certain events, such as changes to the URL and XHR requests to provide context to an error.

You can manually add breadcrumbs on other events or disable breadcrumbs.

from sentry_sdk import add_breadcrumb

    message='Authenticated user %s' %,

For more information, see:

Filter Events & Custom Logic

Sentry exposes a beforeSend callback which can be used to filter out information or add additional context to the event object.

import sentry_sdk

def strip_sensitive_data(event, hint):
    # modify event here
    return event


For more information, see:


Integrations extend the functionality of the SDK for some common frameworks and libraries. Similar to plugins, they extend the functionality of the Sentry SDK. A call to sentry_sdk.init configures integrations. Unless you set default_integrations to False, Sentry automatically adds any default integration not in the list below.

Web Frameworks

Task Queues



Other Integrations

Default Integrations

System integrations are integrations enabled by default that integrate into the standard library or the interpreter itself. Sentry documents them so you can see what they do and that they can be disabled if they cause issues. To disable system integrations, set default_integrations=False when calling init().

For more information, see full documentation on Default Integrations.


The Python SDK provides some common hints for breadcrumbs and events. These hints are passed as the hint parameter to before_send and before_breadcrumb (as well as event processors) as a dictionary. More than one hint can be supplied, but this is rare.

If you set this hint, then it's an exc info tuple in the form (exc_type, exc_value, tb). This can be used to extract additional information from the original error object.

This hint is passed to breadcrumbs and contains the log record that created it. It can be used to extract additional information from the original logging log record that is not extracted by default. Likewise, it can be useful to discard uninteresting breadcrumbs.

An httplib request object for breadcrumbs created from HTTP requests.

Troubleshooting and Known Issues

The Troubleshooting page provides advice for solving known problems.

You can edit this page on GitHub.