From a6705764888042f26fb4065f3fd92a5ef933ec6b Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 7 May 2026 20:20:18 +0000 Subject: [PATCH] docs(webhooks): Document metric_alert.id vs metric_alert.identifier Add missing attribute entries for id and identifier on the metric_alert object. The id is the internal database ID of the incident, while identifier is the organization-scoped sequential incident number used in the Sentry UI and in web_url paths. Fixes DOCS-AQ5 Co-Authored-By: Claude Co-authored-by: Sergiy Dybskiy --- .../integration-platform/webhooks/metric-alerts.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/integrations/integration-platform/webhooks/metric-alerts.mdx b/docs/integrations/integration-platform/webhooks/metric-alerts.mdx index 0907103a547d32..9a22be58d989d2 100644 --- a/docs/integrations/integration-platform/webhooks/metric-alerts.mdx +++ b/docs/integrations/integration-platform/webhooks/metric-alerts.mdx @@ -26,6 +26,16 @@ The interactive demo below shows how to set up an internal integration that can - type: object - description: the incident that triggered the alert rule +### data['metric_alert']['id'] + +- type: string +- description: the internal database ID of the incident + +### data['metric_alert']['identifier'] + +- type: string +- description: the organization-scoped sequential incident number; this value is used in the Sentry UI and appears in the `web_url` path (for example, a `web_url` of `https://sentry.io/organizations/my-org/alerts/1/` corresponds to `identifier: "1"`) + ### data['metric_alert']['alert_rule'] - type: object