An error occurred while fetching the assigned milestone of the selected merge_request.
More information about slack channels in alerting
Compare changes
+ 26
− 2
@@ -23,7 +23,7 @@ The common procedure is as follows:
@@ -31,7 +31,7 @@ ALERT runners_cache_is_down
This will result in a critical alert posted in slack channes `#prometheus-alerts` and `#infrastructure`, pagerduty with a link to https://dev.gitlab.com/cookbooks/runbooks/blob/master/howto/manage-cehpfs.md. Important part is the end or url - `howto/manage-cehpfs.md`. It is taken from annotation `runbook`. Runbook will provide information how to manage situation alerted. Main principle of the runbook should be - `don't make me think`.
This will result in a critical alert posted in slack channes `#prometheus-alerts` and `#production`, pagerduty with a link to https://dev.gitlab.com/cookbooks/runbooks/blob/master/howto/manage-cehpfs.md. Important part is the end or url - `howto/manage-cehpfs.md`. It is taken from annotation `runbook`. Runbook will provide information how to manage situation alerted. Main principle of the runbook should be - `don't make me think`. For channel you can use `#production`, `#ci`, `#gitaly` values.
@@ -70,6 +70,30 @@ All alerts are routed to slack and additionally can be paged to PagerDuty.