diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 12:09:39 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 12:09:39 +0300 |
commit | c52b81f45762cb7f05a950689dfc6d51b197ea73 (patch) | |
tree | c44830c2fc21d13b81814958c44b09fa8d11c805 /doc/user/incident_management | |
parent | 187ee320b39af22929d74c5a2d9b0650bf50a09b (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/incident_management')
-rw-r--r-- | doc/user/incident_management/index.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/user/incident_management/index.md b/doc/user/incident_management/index.md index 829fee47826..2b95128bffd 100644 --- a/doc/user/incident_management/index.md +++ b/doc/user/incident_management/index.md @@ -138,6 +138,4 @@ Incident Management features can be easily enabled & disabled via the Project se #### Auto-creation -GitLab Issues can automatically be created as a result of an Alert notification. An Issue created this way will contain error information to help you further debug the error. - -For [GitLab-managed alerting rules](../project/integrations/prometheus.md#setting-up-alerts-for-prometheus-metrics-ultimate), the issue will include an embedded chart for the query corresponding to the alert. The chart will show an hour of data surrounding the starting point of the incident, 30 minutes before and after. +You can automatically create GitLab issues from an Alert notification. Issues created this way contain error information to help you debug the error. Appropriately configured alerts include an [embedded chart](../project/integrations/prometheus.md#embedding-metrics-based-on-alerts-in-incident-issues) for the query corresponding to the alert. |