debian-mirror-gitlab/doc/operations/incident_management/escalation_policies.md

63 lines
2.3 KiB
Markdown
Raw Normal View History

2021-09-30 23:02:18 +05:30
---
stage: Monitor
2022-04-04 11:22:00 +05:30
group: Respond
2022-11-25 23:54:43 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
2021-09-30 23:02:18 +05:30
---
# Escalation Policies **(PREMIUM)**
2021-11-18 22:05:49 +05:30
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4638) in GitLab 14.1.
2021-09-30 23:02:18 +05:30
Escalation Policies protect your company from missed critical alerts. Escalation Policies contain
time-boxed steps that automatically page the next responder in the escalation step if the responder
in the previous step has not responded. You can create an escalation policy in the GitLab project
where you manage [On-call schedules](oncall_schedules.md).
## Add an escalation policy
2021-10-27 15:23:28 +05:30
Prerequisite:
2021-09-30 23:02:18 +05:30
2022-04-04 11:22:00 +05:30
- You must have at least the Maintainer role.
2021-10-27 15:23:28 +05:30
- You must have an [on-call schedule](oncall_schedules.md).
To create an escalation policy:
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Projects** and find your project.
2021-10-27 15:23:28 +05:30
1. On the left sidebar, select **Monitor > Escalation Policies**.
1. Select **Add an escalation policy**.
1. Enter the policy's name and description, and
2021-09-30 23:02:18 +05:30
escalation rules to follow when a primary responder misses an alert.
1. Select **Add escalation policy**.
![Escalation Policy](img/escalation_policy_v14_1.png)
2021-10-27 15:23:28 +05:30
### Select the responder of an escalation rule
When configuring an escalation rule, you can designate who to page:
- **Email on-call user in schedule:** notifies the users who are on-call when the rule is triggered,
covering all rotations on the specified [on-call schedule](oncall_schedules.md).
- **Email user:** notifies the specified user directly.
When a notification is sent to a user through an on-call schedule or directly, a system note listing
the paged users is created on the alert.
## Edit an escalation policy
2021-09-30 23:02:18 +05:30
2021-10-27 15:23:28 +05:30
To update an escalation policy:
2021-09-30 23:02:18 +05:30
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Projects** and find your project.
2021-10-27 15:23:28 +05:30
1. On the left sidebar, select **Monitor > Escalation Policies**.
1. Select **Edit escalation policy** (**{pencil}**).
1. Edit the information.
1. Select **Save changes**.
2021-09-30 23:02:18 +05:30
2021-10-27 15:23:28 +05:30
## Delete an escalation policy
2021-09-30 23:02:18 +05:30
2021-10-27 15:23:28 +05:30
To delete an escalation policy:
2021-09-30 23:02:18 +05:30
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Projects** and find your project.
2021-10-27 15:23:28 +05:30
1. On the left sidebar, select **Monitor > Escalation Policies**.
1. Select **Delete escalation policy** (**{remove}**).
1. On the confirmation dialog, select **Delete escalation policy**.