Skip to content

Commit 2ea95ad

Browse files
How to resolve On-Call Pages automatically (#30985)
* How to resolve On-Call Pages automatically * remove incorrect content * Apply suggestions from code review Co-authored-by: DeForest Richards <[email protected]> --------- Co-authored-by: DeForest Richards <[email protected]>
1 parent 2f534a1 commit 2ea95ad

File tree

1 file changed

+3
-0
lines changed
  • content/en/service_management/on-call/triggering_pages

1 file changed

+3
-0
lines changed

content/en/service_management/on-call/triggering_pages/_index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ You can send a Page by mentioning a Team's handle with `oncall-` prepended. For
1717

1818
You can send Pages to On-Call Teams wherever @-handles are supported, including monitors, Incident Management, security detection rules, Event Management, and more.
1919

20+
#### Resolving pages automatically
21+
When a monitor recovers, any Page it triggered is automatically set to `Resolved` if the recovery notification includes the On-Call team mention (for example, `@oncall-payments`). If the mention appears only in the alert template (such as within `{{#is_alert}} ... {{/is_alert}}`) and not in the recovery message, the Page does not auto-resolve.
22+
2023
#### Monitors and dynamic urgencies
2124

2225
If you send a Page through a monitor alert, and your Team's routing rule uses dynamic urgencies:

0 commit comments

Comments
 (0)