From a372f69b1d369b400f2465f2b86880d17e555013 Mon Sep 17 00:00:00 2001 From: vivianyentran <20403606+vivianyentran@users.noreply.github.com> Date: Mon, 6 Nov 2023 15:19:04 -0800 Subject: [PATCH] Clarify sentry pagerduty alert config (#8401) * Clarify sentry pagerduty alert config * apply suggestions Co-authored-by: Liza Mock --------- Co-authored-by: Liza Mock --- .../integrations/notification-incidents/pagerduty/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/product/integrations/notification-incidents/pagerduty/index.mdx b/src/docs/product/integrations/notification-incidents/pagerduty/index.mdx index c5b3e46f830d8..b1979d9c52533 100644 --- a/src/docs/product/integrations/notification-incidents/pagerduty/index.mdx +++ b/src/docs/product/integrations/notification-incidents/pagerduty/index.mdx @@ -57,7 +57,7 @@ In [metric alerts](/product/alerts/alert-types/#metric-alerts), select the Pager ![PagerDuty metric alert rule action](pd_metric_alert_rule.png) -If a PagerDuty incident is created from the critical trigger of a metric alert, it will resolve itself when the Sentry metric alert is resolved. +If a PagerDuty incident is created from the critical trigger of a metric alert and no warning threshold has been set, it will resolve itself when the Sentry metric alert is resolved. Metric alerts that have set warning thresholds may need to be manually resolved as PagerDuty incidents. ## Deleting the Legacy PagerDuty Integration