Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install sentry-sdk
- 3. Init with the Epure DSN and verify
DjangoError tracking for Django with sentry-sdk
Use this page when Django should report exceptions through DjangoIntegration. Use /integrations/python for Flask, Celery, and general Python. Use /integrations/fastapi for FastAPI. pip install sentry-sdk, unpinned. Call sentry_sdk.init in settings before Django serves. traces_sample_rate and profiles_sample_rate stay at 0.0.
Host up → install SDK → paste DSN (project id from Settings → SDK connection) → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: sentry-sdk pointing at your Epure DSN, first issue in the list.
Already on Sentry
Keep the SDK. Change the DSN.
- 1. Create an Epure project and copy the DSN
- 2. Replace only the dsn string in init
- 3. Set traces/replay/profile rates to 0
Docs for this stack
The fit
Epure is the error tracker for Django.
Install sentry-sdk once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry-sdk (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What Django hides
View and middleware failures after the process is up.
DjangoIntegration posts unhandled view exceptions. Grouping uses raw frames. Python fixtures are not a per-framework live smoke.
DjangoIntegration
Pass DjangoIntegration() in sentry_sdk.init. The same DSN is the only host change.
Init before serve
Put init in settings.py so it runs before runserver, gunicorn, or uwsgi accepts traffic.
View exceptions
An unhandled raise in a view becomes an issue with the request context the SDK attaches.
Store path fixtures
Python fixtures exercise POST /store/ end to end. That run is not a live Django smoke.
Raw-frame stacks
No Python symbol server. File, function, and line as sentry-sdk sends them.
Install path
Host. SDK. First issue.
New to Sentry or already on it. Same three moves. Official SDK in, DSN pointed at Epure, one test throw.
Run Epure
docker compose up locally (optional `.env` for ports). Register, name a project, copy the DSN from setup or Settings → SDK connection. Self-host is the path that ships today.
Install sentry-sdk
Add the official Sentry SDK from your package manager. Epure speaks the Sentry wire, so there is no @epure/* client.
Init and verify
Call Sentry.init with the Epure DSN. Throw once (or captureException). Confirm 202 and an issue in the list.
Wire path
Init DjangoIntegration before the app serves.
Unpinned sentry-sdk, same as the Python docs. traces_sample_rate and profiles_sample_rate are 0.0.
Install sentry-sdk
Official Sentry client from the package registry. No @epure/* SDK.
Point dsn at Epure
Paste the project DSN from Settings. Fresh install and Sentry migrants use the same field.
Disable discarded lines
Set traces, replay, and profile sample rates to 0. Epure stores exceptions only.
1pip install sentry-sdkWhy Epure
Install sentry-sdk. Point the DSN. Verify.
Keep the official SDK. Change only the host.
Official SDK, no proprietary agent
Install sentry-sdk (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
Honest scope
Exceptions and stacks. We skip replay, profiling, and transaction APM, and never claim 100% compatibility.
Raw-frame grouping
Grouping uses file, function, and line as the SDK sends them. No ProGuard, dSYM, or NDK.
You own the data path
Self-host keeps stack traces on your Postgres. Cloud soft-samples instead of surprise invoices.
FAQ
Before you paste the Django DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry-sdk from the package registry, create an Epure project, paste the DSN, and capture. You need their open SDK client, never their SaaS. Quickstart.
I already use sentry-sdk. Do I rewrite?
No. Leave the SDK. Change only the dsn to your Epure host. Set traces/replay/profile sample rates to 0 so you don’t ship volume Epure discards. Self-host install if you still need compose.
What about transactions, replay, and profiling?
Epure is exception tracking. Transactions are discarded. Replay and profiling items are ignored. Disable those sample rates in init.
How long until I see the first Django issue?
With Docker warm and a DSN in env, most people land a 202 and an issue the same sitting. Persistence is async, so under normal load an issue appears in well under a second.
Which wire path does Django use?
Python fixtures use the legacy store path (POST /store/) and are end to end on that path. They are not a live Django smoke. Envelope also works when sentry-sdk sends it.
How do I verify the first Django issue?
Raise in a view after init has run in settings. Expect HTTP 202, then an issue row. Verify. A rejected DSN: Invalid DSN. A 202 with an empty list: Events not showing. Epure stores exceptions. No session replay, distributed tracing, profiling, or logs.
Point Django at Epure tonight.
Compose up. Install sentry-sdk. Init before Django serves.
Apache 2.0 · official Sentry SDK · swap DSN