2.5 KiB
| stage | group | info |
|---|---|---|
| Monitor | Health | 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 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.
GitLab offers solutions for handling incidents in your applications and services, such as setting up Prometheus alerts, displaying metrics, and sending notifications.
Configure Prometheus alerts
You can set up Prometheus alerts in:
- GitLab-managed Prometheus installations.
- Self-managed Prometheus 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, GitLab creates a unique endpoint which receives a JSON-formatted, customizable payload.
After configuration, you can manage your alerts using either the alerts section or the alert details section.
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 and how to use the available slash commands.
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.
More information
For information about GitLab and incident management, see: