@@ -6,90 +6,17 @@ info: To determine the technical writer assigned to the Stage/Group associated w
...
@@ -6,90 +6,17 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Incidents
# Incidents
While no configuration is required to use the [manual features](#create-an-incident-manually)
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.
of incident management, some simple [configuration](#configure-incidents) is needed to automate incident creation.
For users with at least Guest [permissions](../../user/permissions.md), the
## Incident Creation
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.
-**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](#incident-details) on the incident details page was
[introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229402) in GitLab 13.4.
-**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.
-**Time to SLA** - If configured for this alert, the time remaining
[before the SLA period expires](#service-level-agreement-countdown-timer).
-**Assignees** - The user assigned to the incident.
-**Published** - Displays a green check mark (**{check-circle}**) if the incident is published
to a [Status Page](status_page.md). **(ULTIMATE)**
The Incident list displays incidents sorted by incident created date.
([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229534) 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.
Incidents share the [Issues API](../../user/project/issues/index.md).
You can create an incident manually or automatically.
TIP: **Tip:**
### Create incidents manually
For a live example of the incident list in action, visit this
1. Select the **Activate** check box to activate the integration.
See [Incident List](#incident-list) for a full description of the severities available. Select **Edit** in the right-hand side bar to change the severity of an incident.
1. In **Time limit**, select the length of the SLA period.
1. Click **Save changes**.
### Add a to do
Add a to-do for incidents that you want to track in your to-do list. Clicke the **Add a to do** button at the top of the right-hand side bar to add a to do.
### 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](../../user/project/integrations/slack_slash_commands.md)
and how to [use the available slash commands](../../integration/slash_commands.md).
### Associate Zoom calls
GitLab enables you to [associate a Zoom meeting with an issue](../../user/project/issues/associate_zoom_meeting.md)
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.
### Embed metrics in incidents
You can embed metrics anywhere [GitLab Markdown](../../user/markdown.md) 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](../metrics/embed.md#embedding-gitlab-managed-kubernetes-metrics).
Any changes to the Incident SLA settings are applied to *new* incidents only.
You can embed both [GitLab-hosted metrics](../metrics/embed.md) and
Existing incidents remain unchanged.
[Grafana metrics](../metrics/embed_grafana.md) in incidents and issue
