Sentry

How it works

Sentry Issue Event → Webhook POST → Runframe → Incident Created

Sentry sends issue events to Runframe's webhook endpoint. Runframe parses the payload, maps severity, and creates an incident routed to the linked service and team.

Setup from Runframe

Navigate to Integrations Hub
Click Set up webhook next to Sentry
Link one Runframe service to Sentry
Copy the service-specific webhook URL shown on the Sentry integration page

Setup from Sentry

In Sentry, navigate to Settings > Developer Settings
Create or edit an internal integration with webhook permissions
Paste the Runframe Sentry webhook URL
Enable issue/event webhooks for the projects you want to route into Runframe
Trigger a test issue event and confirm Runframe creates an incident

Keep your webhook URL secure

The routing key in your webhook URL is a secret token. Treat it like a password and avoid pasting it in public tickets, logs, or docs.

Field mapping

Sentry field	Runframe field
Issue title or event title	Incident title
Level	Severity action
Project	Incident metadata
Environment	Incident metadata
Culprit	Description context
Event URL	Source URL

Severity mapping

Configure how Sentry levels map to Runframe incident actions:

Sentry level	Default Runframe action
fatal	Critical (SEV0)
error	Medium (SEV2)
warning	Low (SEV3)
info	Do not create
debug	Do not create

Customize severity mapping

Adjust severity mapping per linked service. For example, you can ignore routine warning events or route only fatal errors to SEV0.

Deduplication

Runframe derives a stable deduplication key from the Sentry issue or event identifiers when available. Repeated events update the same open incident instead of creating duplicates.

Testing

Trigger a test Sentry issue event and verify:

Runframe creates the incident
Title, severity, and service routing are correct
Sentry context is attached
The right team is notified