Merge branch 'sarahwaldner-master-patch-77917' into 'master'

Adding alert_notifications.md to incident management docs

See merge request gitlab-org/gitlab!43897

doc/operations/incident_management/alert_notifications.md

+---
+stage: Monitor
+group: Health
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+---
+
+# Alert notifications
+
+GitLab can react to alerts triggered from your applications. When an alert is
+triggered in GitLab by [managed-Prometheus](../../user/project/integrations/prometheus.md#managed-prometheus-on-kubernetes)
+or triggered using an external source and received with an integration, it's
+important for a responder to be notified.
+
+Responders can receive notifications using the methods described on this page.
+
+## Slack notifications
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) in GitLab 13.1.
+
+You can be alerted by a Slack message when a new alert has been triggered.
+
+For setup information, see the [Slack Notifications Service docs](../../user/project/integrations/slack.md).
+
+## Email notifications
+
+If a project has been [configured to create incidents for triggered alerts](incidents.md#configure-incidents),
+projects members with the _Owner_ or _Maintainer_ role will be sent an email
+notification. To send additional email notifications to project members with the
+Developer role:
+
+1. Navigate to **Settings > Operations**.
+1. Expand the **Incidents** section.
+1. In the **Alert Integration** tab, select the **Send a separate email notification to Developers**
+   check box.
+1. Select **Save changes**.

doc/operations/incident_management/incidents.md

@@ -72,7 +72,7 @@ to create issues when alerts are triggered:
    [Trigger actions from alerts](../metrics/alerts.md#trigger-actions-from-alerts) **(ULTIMATE)**.
 1. To create issues from alerts, select the template in the **Issue Template**
    select box.
-1. To send [separate email notifications](index.md#notify-developers-of-alerts) to users
+1. To send [separate email notifications](alert_notifications.md#email-notifications) to users
    with [Developer permissions](../../user/permissions.md), select
    **Send a separate email notification to Developers**.
 1. Click **Save changes**.

doc/operations/incident_management/index.md

@@ -16,27 +16,6 @@ GitLab offers solutions for handling incidents in your applications and services
 such as [setting up Prometheus alerts](#configure-prometheus-alerts),
 [displaying metrics](./alert_details.md#embed-metrics-in-incidents-and-issues), and sending notifications.
 
-## Alert notifications
-
-### Slack Notifications
-
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) in GitLab 13.1.
-
-You can be alerted via a Slack message when a new alert has been received.
-
-See the [Slack Notifications Service docs](../../user/project/integrations/slack.md) for information on how to set this up.
-
-### Notify developers of alerts
-
-GitLab can react to the alerts triggered from your applications and services
-by creating issues and alerting developers through email. By default, GitLab
-sends these emails to [owners and maintainers](../../user/permissions.md) of the project.
-These emails contain details of the alert, and a link for more information.
-
-To send separate email notifications to users with
-[Developer permissions](../../user/permissions.md), see
-[Configure incidents](./incidents.md#configure-incidents).
-
 ## Configure Prometheus alerts
 
 You can set up Prometheus alerts in: