Route Metric Alerts to incident.io

[serglom21]

Problem Statement

Currently, Sentry's incident.io integration only supports routing issue alerts. This limitation prevents users from leveraging incident.io incident management capabilities for metric alerts. Specifically, it's not possible to:

• Route metric alerts to incident.io for Slack channel notifications or incident creation.
• Differentiate between critical and warning states of metric alerts when notifying incident.io, leading to a lack of granular control over incident response based on severity.

Solution Brainstorm

It would be great if the incident.io integration could be extended to support metric alerts. This could mean:

• Allowing users to configure incident.io as a destination for metric alerts within Sentry's alert rules.
• Providing options to map metric alert severity levels (critical, warning) to specific incident.io incident types or Slack channel notifications.
• Including relevant metric data (value, timestamp, threshold) within the incident.io payload.

Product Area

Alerts

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-alerts for triage ⏲️

[mifu67]

This is something that will be possible once we roll out our Alerts Create Issues refactor (coming in the next couple months).

[Christinarlong]

The ask of adding metric alerts to the Incident.io integration is on Incidentio to implement. They do have alerts (Alert Rule Action) turned on, which means we will send all alert webhooks (i.e both issue alert and metric alert webhooks) to them. From there, it's on Incidentio to support the metric alerts, since we already give them the data.