Introduced in GitLab 13.0.
Incident 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.
Introduced 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 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 of the project. These emails contain details of the alert, and a link for more information.
Configure Prometheus alerts
You can set up Prometheus alerts in:
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, 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.
Integrate issues with Zoom
GitLab enables you to associate a Zoom meeting with an issue 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.
For information about GitLab and incident management, see: