Connect Python with its Sentry SDK
Your Python app keeps its Sentry SDK. Xovris gives it your project’s DSN, and every error it sends becomes a Xovris issue with its stack and release.
pip install sentry-sdkAlready installed? Your code stays as it is – the DSN is the one change.
Start it
Put this where your app starts:
import sentry_sdk
# reads SENTRY_DSN from the environmentsentry_sdk.init()It reads SENTRY_DSN, so your project’s address never sits in your code.
Your project’s DSN
Xovris finds the SDK in your requirements.txt, creates your project’s address and writes it as SENTRY_DSN in your env file, after showing you the change. It then sends a test event and waits until it is stored. In the project, run:
npx xovris@latest initnpx xovris@latest initnpx xovris@latest initSee the first error
Send one from anywhere your app runs:
sentry_sdk.capture_exception(Exception("first error for Xovris"))Capture one error with the SDK’s own call and it appears as a Xovris issue:
- Errors and their stack traces, grouped into issues
- Messages you capture
- The release each event names
What Xovris has run
Driven with the real SDK: sentry-sdk 2.71.0, captured 2026-10-03 (Brotli-compressed envelopes, an attachment, structured logs). Its own bytes are replayed into Xovris on every change.
Every option the SDK has is in its own documentation: docs.sentry.io/platforms/python/
Traces and metrics too
Xovris also sets Python up with OpenTelemetry for traces, metrics and logs beside the SDK’s errors. Connect Python (Django, FastAPI, Flask) with OpenTelemetry
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.