This guide focuses on plain Python. If you're working with Django, FastAPI, Starlette, or any other web framework, choose the respective guide from the list of supported frameworks.
Error Monitoring starts working as soon as you call sentry_sdk.init(). Logs and Application Metrics need no extra configuration when using sentry_sdk.logger and sentry_sdk.metrics, and you'll learn how to send them in steps #3 and #4. This guide also enables Tracing and Profiling.
Want to learn more about these features?
Issues (always enabled): Sentry's core error monitoring product that automatically reports errors, uncaught exceptions, and crashes. If you have something that looks like an exception, Sentry can capture it.
Tracing: Track software performance while seeing the impact of errors across multiple systems. For example, distributed tracing allows you to follow a request from the frontend to the backend and back. On the server, this includes Agent Tracing: supported AI libraries are instrumented automatically, so you can see model calls, tool executions, and token usage.
Profiling: Gain deeper insight than traditional tracing without custom instrumentation, letting you discover slow-to-execute or resource-intensive functions in your app.
Logs: Centralize and analyze your application logs to correlate them with errors and performance issues. Search, filter, and visualize log data to understand what's happening in your applications.
Application Metrics (always enabled): Track and analyze custom application metrics, such as response times and database query durations, to understand trends and patterns in your application's performance and behavior over time.
Don't need a feature? Remove its options from the snippet.
Copied
import sentry_sdk
sentry_sdk.init( dsn="___PUBLIC_DSN___",# Check https://docs.sentry.io/platforms/python/data-management/data-collected/ to configure what data is collected data_collection={"user_info":True,},# Enables Tracing.# Set to 1.0 to capture 100% of spans for tracing.# We recommend reducing this value in production. traces_sample_rate=1.0,# Enables Profiling.# Set to 1.0 to profile 100% of sessions. profile_session_sample_rate=1.0,# Profiles are collected while a transaction is active. profile_lifecycle="trace",)
import sentry_sdk
sentry_sdk.init( dsn="___PUBLIC_DSN___",# Check https://docs.sentry.io/platforms/python/data-management/data-collected/ to configure what data is collected data_collection={"user_info":True,},# Enables Tracing.# Set to 1.0 to capture 100% of spans for tracing.# We recommend reducing this value in production. traces_sample_rate=1.0,# Enables Profiling.# Set to 1.0 to profile 100% of sessions. profile_session_sample_rate=1.0,# Profiles are collected while a transaction is active. profile_lifecycle="trace",)
In async programs, add the AsyncioIntegration to instrument your async code. This integration isn't enabled by default. Call sentry_sdk.init() at the beginning of the first async function you call:
Copied
import asyncio
import sentry_sdk
from sentry_sdk.integrations.asyncio import AsyncioIntegration
asyncdefmain(): sentry_sdk.init(...,# same options as above integrations=[AsyncioIntegration()],)asyncio.run(main())
import asyncio
import sentry_sdk
from sentry_sdk.integrations.asyncio import AsyncioIntegration
asyncdefmain(): sentry_sdk.init(...,# same options as above integrations=[AsyncioIntegration()],)asyncio.run(main())
The Sentry SDK automatically enables integrations for many popular libraries, so operations like HTTP requests or database queries made with supported libraries will be captured as spans automatically.
However, spans are only created within an existing transaction. If you're not using a supported framework that creates transactions automatically, you'll need to create them manually using sentry_sdk.start_transaction().
Use sentry_sdk.logger to send structured logs at different levels. You can include searchable attributes with each message.
To capture records from Python's standard-library logging module or Loguru, configure capture_sentry_logs=True on the corresponding integration. See the standard logging and Loguru integration guides.
See Set Up Logs for all available logging methods and formatting options.
The SDK sends profiles after a transaction finishes, so a script that exits right away, like the one above, might not send a profile. Profiles appear for applications that keep running after their transactions complete.
Now, head over to your project on Sentry.io to view the collected data (it takes a couple of moments for the data to appear).
Need help locating captured data in your Sentry project?
Open the Issues page and select an error from the issues list to view the full details and context of this error. For more details, see the Issue Details documentation.
Open the Traces page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click here.
Open the Profiles page to see your slowest functions and an aggregate flame graph of your most frequent code paths. If tracing is enabled, select a transaction to see the flame graph for that part of your app. For more information, click here.
Open the Logs page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click here.
Help improve this content Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.