diff options
Diffstat (limited to 'doc/operations/incident_management/alerts.md')
| -rw-r--r-- | doc/operations/incident_management/alerts.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/operations/incident_management/alerts.md b/doc/operations/incident_management/alerts.md index e701fb2e5fb..e558462cad7 100644 --- a/doc/operations/incident_management/alerts.md +++ b/doc/operations/incident_management/alerts.md @@ -4,7 +4,7 @@ group: Respond 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 --- -# Alerts **(FREE)** +# Alerts **(FREE ALL)** Alerts are a critical entity in your incident management workflow. They represent a notable event that might indicate a service outage or disruption. GitLab provides a list view for triage and detail view for deeper investigation of what happened. @@ -153,7 +153,7 @@ When you [close an incident](manage_incidents.md#close-an-incident) that is link GitLab [changes the alert's status](#change-an-alerts-status) to **Resolved**. You are then credited with the alert's status change. -#### As an on-call responder **(PREMIUM)** +#### As an on-call responder **(PREMIUM ALL)** On-call responders can respond to [alert pages](paging.md#escalating-an-alert) by changing the alert status. @@ -206,7 +206,7 @@ from an alert, and view it later on your **To-Do List**. To add a to-do item, on the right sidebar, select **Add a to do**. -### Trigger actions from alerts **(ULTIMATE)** +### Trigger actions from alerts **(ULTIMATE ALL)** > - Introduced in GitLab 13.1: incidents are not created automatically by default. > - Mapping common severity values from the alert payload [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50871) in GitLab 13.9. |