summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Leitzen <pleitzen@gitlab.com>2019-07-24 10:51:59 +0200
committerPeter Leitzen <pleitzen@gitlab.com>2019-07-24 16:23:56 +0200
commit444bb45673b04531fdaea4f0a4c82d6ae22c72ff (patch)
tree09d28def3c382a7a5cd38f6570eb537b43199b82
parent2a07275121b9c965bca01767c5ccdb58c6f6e660 (diff)
downloadgitlab-ce-pl-label-incident-issues-docs.tar.gz
-rw-r--r--doc/user/project/integrations/prometheus.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/user/project/integrations/prometheus.md b/doc/user/project/integrations/prometheus.md
index 61c30e0b0ef..ba982c9cf6f 100644
--- a/doc/user/project/integrations/prometheus.md
+++ b/doc/user/project/integrations/prometheus.md
@@ -326,6 +326,8 @@ Once enabled, an issue will be opened automatically when an alert is triggered w
To further customize the issue, you can add labels, mentions, or any other supported [quick action](../quick_actions.md) in the selected issue template.
+Since [version 12.2](https://gitlab.com/gitlab-org/gitlab-ce/issues/63373), GitLab will tag each incident issue with the `incident` label automatically. If the label does not yet exist, it will be created automatically as well.
+
If the metric exceeds the threshold of the alert for over 5 minutes, an email will be sent to all [Maintainers and Owners](../../permissions.md#project-members-permissions) of the project.
## Determining the performance impact of a merge