/Integrations
v1.2Sentry
Validate Sentry DSN delivery with a synthetic heartbeat event.
Integration
Sentry
Confirms Sentry DSN delivery with a synthetic heartbeat.
An invalid or stale DSN means production errors vanish silently—you only discover observability gaps during your first real incident. PreFlight parses your DSN, sends a synthetic heartbeat event, and records provider response status so you know errors will reach the dashboard before launch day.
Requirements
- Sentry DSN from the production project your app reports to
- Environment name (for example `production` or `staging`)
- Optional Sentry auth token, organization slug, and project slug for extended API checks
What PreFlight checks
| Probe | What it proves |
|---|---|
| DSN parsing | The DSN project ID and public key are valid and well-formed. |
| Synthetic heartbeat | A test event is accepted by Sentry ingest. |
| Provider response | Safe status and response metadata are recorded without logging secrets. |
| Environment tagging | Events arrive with the configured environment label. |
Failure guidance
| Symptom | Fix |
|---|---|
| DSN rejected | Copy the current DSN from the production Sentry project—not a deleted or rotated project. |
| Event not visible | Check Sentry → Issues after a successful probe; the heartbeat is intentionally visible. |
| Wrong project | Confirm the DSN matches the project your deployed SDK initializes with. |
| Rate limited | Wait and retry, or confirm you are not pointing multiple environments at one overloaded key. |
Dashboard setup
- Navigate to Integrations → Sentry in your PreFlight project.
- Paste the DSN from Sentry → Settings → Client Keys (DSN).
- Set the environment name to match your production SDK configuration.
- Run Pre-Flight Check and confirm the heartbeat appears in Sentry Issues.