Incidents (FREE)

Incidents are critical entities in incident management workflows. They represent a service disruption or outage that needs to be restored urgently. GitLab provides tools for the triage, response, and remediation of incidents.

Users with at least Guest permissions can access incidents on public projects.

Incident creation

You can create an incident manually or automatically.

Create incidents manually

• Moved to GitLab Free in 13.3.
• Permission changed from Guest to Reporter in GitLab 14.5.
• Automatic application of the incident label removed in GitLab 14.8.

If you have at least Reporter permissions, you can create an incident manually from the Incidents List or the Issues List.

To create an incident from the Incidents List:

1. Navigate to Monitor > Incidents and select Create Incident.
2. Create a new issue using the incident template.

To create an incident from the Issues List:

Introduced in GitLab 13.4.

1. Go to Issues > List, and select New issue.
2. In the Type dropdown, select Incident. Only fields relevant to incidents are displayed on the page.
3. Create the incident as needed, and select Create issue to save the incident.

Create incidents automatically (ULTIMATE)

With at least the Maintainer role, you can enable GitLab to create incident automatically whenever an alert is triggered:

1. Navigate to Settings > Monitor > Incidents and expand Incidents.
2. Check the Create an incident checkbox.
3. To customize the incident, select an issue template, to include in the incident summary.
4. To send an email notification to users with the Developer role, select Send a separate email notification to Developers. Email notifications are also sent to users with the Maintainer and Owner roles.
5. Select Save changes.

Create incidents via the PagerDuty webhook

Introduced in GitLab 13.3.

You can set up a webhook with PagerDuty to automatically create a GitLab incident for each PagerDuty incident. This configuration requires you to make changes in both PagerDuty and GitLab:

1. Sign in as a user with the Maintainer role.

2. Navigate to Settings > Monitor > Incidents and expand Incidents.

3. Select the PagerDuty integration tab:

   

4. Activate the integration, and save the changes in GitLab.

5. Copy the value of Webhook URL for use in a later step.

6. Follow the steps described in the PagerDuty documentation to add the webhook URL to a PagerDuty webhook integration.

To confirm the integration is successful, trigger a test incident from PagerDuty to confirm that a GitLab incident is created from the incident.

Incident list

For users with at least Guest permissions, the Incident list is available at Monitor > Incidents in your project's sidebar. The list contains the following metrics:

• State - To filter incidents by their state, select Open, Closed, or All above the incident list.

• Search - The Incident list supports a simple free text search, which filters on the Title and Incident fields.

• Severity - Severity of a particular incident, which can be one of the following values:

  • {severity-critical} Critical - S1
  • {severity-high} High - S2
  • {severity-medium} Medium - S3
  • {severity-low} Low - S4
  • {severity-unknown} Unknown

  Editing incident severity on the incident details page was introduced in GitLab 13.4.

• Incident - The description of the incident, which attempts to capture the most meaningful data.

• Status - The status of the incident, which can be one of the following values:

  • Triggered
  • Acknowledged
  • Resolved

  In GitLab Premium, this field is also linked to on-call escalation for the incident.

• Date created - How long ago the incident was created. This field uses the standard GitLab pattern of X time ago, but is supported by a granular date/time tooltip depending on the user's locale.

• Assignees - The user assigned to the incident.

• Published - Displays a green check mark ({check-circle}) if the incident is published to a Status Page.

The Incident list displays incidents sorted by incident created date. (Introduced in GitLab 13.3.) To see if a column is sortable, point your mouse at the header. Sortable columns display an arrow next to the column name.

Incidents share the Issues API.

NOTE: For a live example of the incident list in action, visit this demo project.

Incident details

Introduced in GitLab 13.4.

Users with at least Guest permissions can view the Incident Details page. Navigate to Monitor > Incidents in your project's sidebar, and select an incident from the list.

When you take any of these actions on an incident, GitLab logs a system note and displays it in the Incident Details view:

• Updating the severity of an incident (Introduced in GitLab 13.5.)

For live examples of GitLab incidents, visit the tanuki-inc project's incident list page. Select any incident in the list to display its incident details page.

Summary

The summary section for incidents provides both critical details about the incident and the contents of the issue template (if applicable). The highlighted bar at the top of the incident displays from left to right:

• The link to the original alert.
• The alert start time.
• The event count.

Beneath the highlight bar, GitLab displays a summary that includes the following fields:

• Start time
• Severity
• full_query
• Monitoring tool

The incident summary can be further customized using GitLab Flavored Markdown. If the corresponding alert provided Markdown for the incident, then the Markdown is appended to the summary after the above alert fields. If an incident template is configured for the project, then the template content is appended at the end.

Comments are displayed in threads, but can be displayed chronologically by toggling on the recent updates view.

Metrics (PREMIUM)

Introduced in GitLab 13.8.

In many cases, incidents are associated to metrics. You can upload screenshots of metric charts in the Metrics tab:

When you upload an image, you can associate the image with text or a link to the original graph.

If you add a link, you can access the original graph by clicking the hyperlink above the uploaded image.

Alert details

Incidents show the details of linked alerts in a separate tab. To populate this tab, the incident must have been created with a linked alert. Incidents created automatically from alerts have this field populated.

Timeline events

Incident timelines give a high-level overview of what happened during an incident, and the steps that were taken for it to be resolved.

Read more about timeline events and how to enable this feature.

Recent updates view (PREMIUM)

Introduced in GitLab 13.5.

To quickly see the latest updates on an incident, select {history} Turn recent updates view on in the comment bar to display comments un-threaded and ordered chronologically, newest to oldest:

Service Level Agreement countdown timer (PREMIUM)

Introduced in GitLab 13.5.

You can enable the Service Level Agreement Countdown timer on incidents to track the Service Level Agreements (SLAs) you hold with your customers. The timer is automatically started when the incident is created, and shows the time remaining before the SLA period expires. The timer is also dynamically updated every 15 minutes so you do not have to refresh the page to see the time remaining. To configure the timer:

1. Navigate to Settings > Monitor.
2. Scroll to Incidents and select Expand, then select the Incident settings tab.
3. Select Activate "time to SLA" countdown timer.
4. Set a time limit in increments of 15 minutes.
5. Select Save changes.

After you enable the SLA countdown timer, the Time to SLA attribute is displayed as a column in the Incidents List, and as a field on newly created Incidents. If the incident isn't closed before the SLA period ends, GitLab adds a missed::SLA label to the incident.

Assign incidents

Assign incidents to users that are actively responding. Select Edit in the right-hand side bar to select or clear assignees.

Associate a milestone

Associate an incident to a milestone by selecting Edit next to the milestone feature in the right-hand side bar.

Change severity

See Incident List for a full description of the severity levels available. Select Edit in the right-hand side bar to change the severity of an incident.

You can also change the severity using the /severity quick action.

Add a to-do item

Add a to-do for incidents that you want to track in your to-do list. Select Add a to do at the top of the right-hand side bar to add a to-do item.

Change incident status

• Introduced in GitLab 14.9 with a flag named incident_escalations. Disabled by default.
• Enabled on GitLab.com and self-managed in GitLab 14.10.
• Feature flag incident_escalations removed in GitLab 15.1.

For users with the Developer role or higher, select Edit in the Status section of the right-hand side bar of an incident, then select a status. Triggered is the default status for new incidents.

In projects with GitLab Premium, on-call responders can respond to incident pages by changing the status. Setting the status to:

• Resolved silences on-call pages for the alert.
• Acknowledged limits on-call pages based on the selected escalation policy.
• Triggered from Resolved restarts the incident escalating from the beginning.

In GitLab 15.1 and earlier, updating the status of an incident created from an alert also updates the alert status. In GitLab 15.2 and later, the alert status is independent and does not update when the incident status changes.

Change escalation policy (PREMIUM)

• Introduced in GitLab 14.9 with a flag named incident_escalations. Disabled by default.
• Enabled on GitLab.com and self-managed in GitLab 14.10.
• Feature flag incident_escalations removed in GitLab 15.1.

For users with the Developer role or higher, select Edit in the Escalation policy section of the right-hand side bar of an incident, then select a policy. By default, new incidents do not have an escalation policy selected.

Selecting an escalation policy updates the incident status to Triggered and begins escalating the incident to on-call responders. Deselecting an escalation policy halts escalation. Refer to the incident status to manage on-call paging once escalation has begun.

In GitLab 15.1 and earlier, the escalation policy for incidents created from alerts reflects the alert's escalation policy and cannot be changed. In GitLab 15.2 and later, the incident escalation policy is independent and can be changed.

Manage incidents from 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.

Associate Zoom calls

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.

Linked resources

In an incident, you can add links to various resources, for example:

• The incident Slack channel
• Zoom meeting
• Resources for resolving the incidents

Embed metrics in incidents

You can embed metrics anywhere GitLab Markdown is used, such as descriptions, comments on issues, and merge requests. Embedding metrics helps you share them when discussing incidents or performance issues. You can output the dashboard directly into any issue, merge request, epic, or any other Markdown text field in GitLab by copying and pasting the link to the metrics dashboard.

You can embed both GitLab-hosted metrics and Grafana metrics in incidents and issue templates.

Automatically close incidents via recovery alerts

• Introduced for Prometheus Integrations in GitLab 12.5.
• Introduced for HTTP Integrations in GitLab 13.4.

With at least the Maintainer role, you can enable GitLab to close an incident automatically when a Recovery Alert is received:

1. Navigate to Settings > Monitor > Incidents and expand Incidents.
2. Check the Automatically close associated Incident checkbox.
3. Select Save changes.

When GitLab receives a Recovery Alert, it closes the associated incident. This action is recorded as a system message on the incident indicating that it was closed automatically by the GitLab Alert bot.