IncidentRelay
Sentry integration

Route Sentry issue and metric alerts through IncidentRelay.

Sentry routes use a route-scoped webhook URL and Client Secret verification before alerts enter the IncidentRelay routing workflow.

Read Sentry docs Troubleshooting

Route-scoped webhook setup

Unlike token-based integrations, Sentry sends to a route-specific endpoint. IncidentRelay verifies the Sentry signature using the route's saved Client Secret and then applies the route configuration.

Useful Sentry labels

  • project_slug for project-based routing.
  • environment for production or staging separation.
  • issue_id for grouping.
  • level or normalized severity for channel filtering.

Example matcher

{
  "labels": {
    "project_slug": "backend",
    "environment": "production"
  }
}

Responder workflow

After routing, Sentry alerts follow the same IncidentRelay lifecycle as other alerts: assignment, notifications, acknowledgement, resolution, comments and escalation.