2020-08-18 17:09:57 -04:00
---
stage: Monitor
group: Health
info: 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
---
2020-10-08 20:08:41 -04:00
# Incidents
2020-08-18 17:09:57 -04:00
While no configuration is required to use the [manual features ](#create-an-incident-manually )
of incident management, some simple [configuration ](#configure-incidents ) is needed to automate incident creation.
2020-09-30 17:10:09 -04:00
For users with at least Guest [permissions ](../../user/permissions.md ), the
2020-08-18 17:09:57 -04:00
Incident Management list is available at **Operations > Incidents**
in your project's sidebar. The list contains the following metrics:
2020-09-11 08:08:50 -04:00
![Incident List ](img/incident_list_v13_4.png )
2020-08-18 17:09:57 -04:00
- **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.
2020-09-15 08:09:30 -04:00
- **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**
2020-10-08 20:08:41 -04:00
[Editing incident severity ](#incident-details ) on the incident details page was
2020-09-24 14:09:51 -04:00
[introduced ](https://gitlab.com/gitlab-org/gitlab/-/issues/229402 ) in GitLab 13.4.
2020-09-15 08:09:30 -04:00
2020-08-18 17:09:57 -04:00
- **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
2020-09-15 08:09:30 -04:00
to a [Status Page ](status_page.md ). ** (ULTIMATE)**
2020-08-18 17:09:57 -04:00
The Incident list displays incidents sorted by incident created date.
2020-09-15 08:09:30 -04:00
([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229534) to GitLab core in 13.3.)
2020-08-18 17:09:57 -04:00
To see if a column is sortable, point your mouse at the header. Sortable columns
display an arrow next to the column name.
2020-10-08 20:08:41 -04:00
Incidents share the [Issues API ](../../user/project/issues/index.md ).
2020-09-03 14:08:29 -04:00
TIP: **Tip:**
For a live example of the incident list in action, visit this
[demo project ](https://gitlab.com/gitlab-examples/ops/incident-setup/everyone/tanuki-inc/-/incidents ).
2020-08-18 17:09:57 -04:00
## Configure incidents
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4925) in GitLab Ultimate 11.11.
With Maintainer or higher [permissions ](../../user/permissions.md ), 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** :
2020-09-02 14:10:40 -04:00
![Incident Management Settings ](./img/incident_management_settings_v13_3.png )
2020-08-18 17:09:57 -04:00
1. 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 ](../../user/project/description_templates.md#creating-issue-templates ).
For more information, see
2020-09-07 11:09:04 -04:00
[Trigger actions from alerts ](../metrics/alerts.md#trigger-actions-from-alerts ) ** (ULTIMATE)**.
2020-08-18 17:09:57 -04:00
1. To create issues from alerts, select the template in the **Issue Template**
select box.
2020-09-30 20:10:16 -04:00
1. To send [separate email notifications ](alert_notifications.md#email-notifications ) to users
2020-08-18 17:09:57 -04:00
with [Developer permissions ](../../user/permissions.md ), select
**Send a separate email notification to Developers** .
1. Click **Save changes** .
Appropriately configured alerts include an
[embedded chart ](../metrics/embed.md#embedding-metrics-based-on-alerts-in-incident-issues )
for the query corresponding to the alert. You can also configure GitLab to
2020-09-07 11:09:04 -04:00
[close issues ](../metrics/alerts.md#trigger-actions-from-alerts )
2020-08-18 17:09:57 -04:00
when you receive notification that the alert is resolved.
## Create an incident manually
2020-09-22 14:09:54 -04:00
If you have at least Guest [permissions ](../../user/permissions.md ), to create an Incident, you have two options.
2020-09-09 08:08:22 -04:00
### From the Incidents List
2020-08-18 17:09:57 -04:00
2020-09-09 08:08:22 -04:00
> [Moved](https://gitlab.com/gitlab-org/monitor/health/-/issues/24) to GitLab core in 13.3.
2020-08-18 17:09:57 -04:00
- 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.
2020-09-09 08:08:22 -04:00
![Incident List Create ](./img/incident_list_create_v13_3.png )
### From the Issues List
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230857) in GitLab 13.4.
- Navigate to **Issues > List** and click **Create Issue** .
- Create a new issue using the `type` drop-down and select `Incident` .
2020-09-15 08:09:30 -04:00
- The page refreshes and the page only displays fields relevant to Incidents.
2020-09-09 08:08:22 -04:00
![Incident List Create ](./img/new_incident_create_v13_4.png )
2020-08-18 17:09:57 -04:00
## Configure PagerDuty integration
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/119018) 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 ](../../user/permissions.md ).
1. Navigate to **Settings > Operations > Incidents** and expand **Incidents** .
1. Select the **PagerDuty integration** tab:
2020-09-02 14:10:40 -04:00
![PagerDuty incidents integration ](./img/pagerduty_incidents_integration_v13_3.png )
2020-08-18 17:09:57 -04:00
1. Activate the integration, and save the changes in GitLab.
1. Copy the value of **Webhook URL** for use in a later step.
1. Follow the steps described in the
[PagerDuty documentation ](https://support.pagerduty.com/docs/webhooks )
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.
2020-09-16 23:09:42 -04:00
## Incident details
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230847) in GitLab 13.4.
2020-10-08 20:08:41 -04:00
Users with at least Reporter [permissions ](../../user/permissions.md ) can view
the Incident Details page. Navigate to **Operations > 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](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42358) in GitLab 13.5.)
For live examples of GitLab incidents, visit the `tanuki-inc` project's
[incident list page ](https://gitlab.com/gitlab-examples/ops/incident-setup/everyone/tanuki-inc/-/incidents ).
Click any incident in the list to display its incident details page.
2020-09-17 17:09:39 -04:00
### Summary
The summary section for incidents provides both critical details about and the
contents of the issue template (if one was used). The highlighted bar at the top
2020-10-08 20:08:41 -04:00
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:
2020-09-17 17:09:39 -04:00
- Start time
- Severity
- `full_query`
- Monitoring tool
2020-10-08 20:08:41 -04:00
Comments are displayed in threads, but can be displayed chronologically
[in a timeline view ](#timeline-view ).
2020-09-17 17:09:39 -04:00
### Alert details
2020-09-16 23:09:42 -04:00
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
2020-10-08 20:08:41 -04:00
[created automatically ](#configure-incidents ) from alerts have this
2020-09-16 23:09:42 -04:00
field populated.
![Incident alert details ](./img/incident_alert_details_v13_4.png )
2020-10-08 20:08:41 -04:00
### Timeline view
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227836) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.5.
To quickly see the latest updates on an incident, click
**{comments}** **Turn timeline view on** in the comment bar to display comments
un-threaded and ordered chronologically, newest to oldest:
![Timeline view toggle ](./img/timeline_view_toggle_v13_5.png )