Create and manage incidents in GitLab

While no configuration is required to use the manual features of incident management, some simple configuration is needed to automate incident creation.

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

• Status - To filter incidents by their status, click 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.
• Incident - The description of the incident, which attempts to capture the most meaningful data.
• 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.. (ULTIMATE)

The Incident list displays incidents sorted by incident created date. (Introduced to GitLab core in 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.

NOTE: Note: Incidents share the Issues API.

Configure incidents

Introduced in GitLab Ultimate 11.11.

With Maintainer or higher permissions, you can enable or disable Incident Management features in the GitLab user interface to create issues when alerts are triggered:

1. Navigate to Settings > Operations > Incidents and expand Incidents:

   

2. For GitLab versions 11.11 and greater, you can select the Create an issue checkbox to create an issue based on your own issue templates. For more information, see Trigger actions from alerts (ULTIMATE).

3. To create issues from alerts, select the template in the Issue Template select box.

4. To send separate email notifications to users with Developer permissions, select Send a separate email notification to Developers.

5. Click Save changes.

Appropriately configured alerts include an embedded chart for the query corresponding to the alert. You can also configure GitLab to close issues when you receive notification that the alert is resolved.

Create an incident manually

Moved to GitLab core in 13.3.

For users with at least Developer permissions, to create a Incident you can take any of the following actions:

• Navigate to Operations > Incidents and click Create Incident.
• Create a new issue using the incident template available when creating it.
• Create a new issue and assign the incident label to it.

Configure PagerDuty integration

Introduced in GitLab 13.3.

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

1. Sign in as a user with Maintainer permissions.

2. Navigate to Settings > Operations > 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 issue is created from the incident.