diff options
Diffstat (limited to 'doc/operations/incident_management/paging.md')
| -rw-r--r-- | doc/operations/incident_management/paging.md | 23 |
1 files changed, 12 insertions, 11 deletions
diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md index dcb17048d35..70c67977b73 100644 --- a/doc/operations/incident_management/paging.md +++ b/doc/operations/incident_management/paging.md @@ -14,12 +14,11 @@ notifications using the methods described on this page. > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) in GitLab 13.1. -Responders can be paged via Slack using the -[Slack Notifications Service](../../user/project/integrations/slack.md), which you -can configure for new alerts and new incidents. After configuring, responders -receive a **single** page via Slack. To set up Slack notifications on your mobile -device, make sure to enable notifications for the Slack app on your phone so -you never miss a page. +The GitLab for Slack app can be used to receive important incident notifications. + +When [the GitLab for Slack app is configured](slack.md), incident responders are notified in Slack +every time a new incident is declared. To ensure you don't miss any important incident notifications +on your mobile device, enable notifications for Slack on your phone. ## Email notifications for alerts @@ -55,12 +54,14 @@ or stop alert escalations by [updating the alert's status](alerts.md#change-an-a > - [Feature flag `incident_escalations`](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) removed in GitLab 15.1. For incidents, paging on-call responders is optional for each individual incident. -To begin escalating the incident, [set the incident's escalation policy](incidents.md#change-escalation-policy). + +To begin escalating the incident, [set the incident's escalation policy](manage_incidents.md#change-escalation-policy). + For each escalation rule, the designated on-call responders receive one email when -the rule fires. You can respond to a page or stop incident escalations by -[updating the incident's status](incidents.md#change-incident-status) or, if applicable, -[unsetting the incident's escalation policy](incidents.md#change-escalation-policy). +the rule fires. Respond to a page or stop incident escalations by +[changing the incident's status](manage_incidents.md#change-status) or +changing the incident's escalation policy back to **No escalation policy**. -In GitLab 15.1 and earlier, [incidents created from alerts](alerts.md#create-an-incident-from-an-alert) +In GitLab 15.1 and earlier, [incidents created from alerts](manage_incidents.md#from-an-alert) do not support independent escalation. In [GitLab 15.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/356057), all incidents can be escalated independently. |