Sentry Integration

The Sentry integration brings your error monitoring data into BlameTrail. When Sentry detects issues or fires alerts, BlameTrail automatically creates and manages incidents, enriches them with Sentry event data, and correlates them with your deploy history for suspect scoring.

Integration modes

BlameTrail supports two modes for connecting to Sentry, depending on your setup:

Internal integration

Best for teams using a single Sentry organization. You create an internal integration in Sentry's Developer Settings, copy the auth token, and paste it into BlameTrail.

• Manual token configuration
• No token refresh needed (internal tokens do not expire)
• Simpler setup, fewer moving parts

See Internal Integration Setup for step-by-step instructions.

Public / OAuth integration

Best for platforms serving multiple organizations or teams that prefer OAuth-based authentication. Users connect via an OAuth flow, and BlameTrail manages token refresh automatically.

• OAuth-based authentication
• Automatic token refresh
• Multiple organizations can connect independently

See OAuth Integration Setup for step-by-step instructions.

What the integration does

Once connected, the Sentry integration provides:

Webhook-driven incidents

Sentry sends webhooks for issues and alert rule triggers. BlameTrail normalizes these events into its incident model, automatically creating and resolving incidents based on Sentry issue status changes.

Event enrichment

When a Sentry-originated incident is created, BlameTrail fetches additional context from the Sentry API:

• Tags — Environment, release, browser, OS, and other event tags
• Stacktraces — Exception details and stack frames from the latest event
• Event metadata — Timestamps, user context, and breadcrumbs

This enrichment data is displayed on the incident detail page alongside BlameTrail's own monitoring data.

Project mappings

Sentry projects are mapped to BlameTrail services, so webhooks create incidents on the correct service. Unmapped projects are ignored. See Project Mappings.

Issue links

Bi-directional linking between Sentry issues and BlameTrail incidents. Link from the Sentry UI or view linked issues on the BlameTrail incident page. See Issue Links.

Alert rule actions

Configure Sentry alert rules to create BlameTrail incidents with specific severity, service targeting, and environment filters. See Alert Rules.

Architecture

Sentry Issue/Alert
       |
       v
  Webhook (HMAC-verified)
       |
       v
  Normalization Queue
       |
       v
  Incident Creation / Update
       |
       v
  Enrichment Queue (async)
       |
       v
  Tags, Stacktraces, Event Data

Webhooks are verified using HMAC signatures with the client secret you configure during setup. After verification, events are placed on a normalization queue for async processing. Enrichment runs as a separate background job to avoid blocking the webhook response.

Next steps

• Internal Integration Setup — Single-org setup with a manual token
• OAuth Integration Setup — Multi-org setup with automatic token refresh
• Project Mappings — Route Sentry projects to BlameTrail services
• Issue Links — Link Sentry issues to BlameTrail incidents
• Alert Rules — Trigger BlameTrail incidents from Sentry alert rules