Add latest changes from gitlab-org/gitlab@13-3-stable-ee

1 files changed, 68 insertions, 0 deletions

diff --git a/doc/operations/incident_management/index.md b/doc/operations/incident_management/index.md
new file mode 100644
index 00000000000..53a6b47ec4b
--- /dev/null
+++ b/doc/operations/incident_management/index.md
@@ -0,0 +1,68 @@
+---
+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
+---
+
+# Incident management
+
+> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2877) in GitLab 13.0.
+
+Alert Management enables developers to easily discover and view the alerts
+generated by their application. By surfacing alert information where the code is
+being developed, efficiency and awareness can be increased.
+
+GitLab offers solutions for handling incidents in your applications and services,
+such as [setting up Prometheus alerts](#configure-prometheus-alerts),
+[displaying metrics](alertdetails.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:
+
+- [GitLab-managed Prometheus](../metrics/alerts.md) installations.
+- [Self-managed Prometheus](../metrics/alerts.md#external-prometheus-instances) installations.
+
+Prometheus alerts are created by the special Alert Bot user. You can't remove this
+user, but it does not count toward your license limit.
+
+## Configure external generic alerts
+
+GitLab can accept alerts from any source through a generic webhook receiver. When
+[configuring the generic alerts integration](../../user/project/integrations/generic_alerts.md),
+GitLab creates a unique endpoint which receives a JSON-formatted, customizable payload.
+
+## Integrate incidents with Slack
+
+Slack slash commands allow you to control GitLab and view GitLab content without leaving Slack.
+
+Learn how to [set up Slack slash commands](../../user/project/integrations/slack_slash_commands.md)
+and how to [use the available slash commands](../../user/project/slash_commands.md).
+
+## Integrate issues with Zoom
+
+GitLab enables you to [associate a Zoom meeting with an issue](../../user/project/issues/associate_zoom_meeting.md)
+for synchronous communication during incident management. After starting a Zoom
+call for an incident, you can associate the conference call with an issue. Your
+team members can join the Zoom call without requesting a link.