- Incident Creation
- Incident list
- Incident details
Incidents are critical entities in incident management workflows. They represent a service disruption or outage that needs to be restored urgently. WVS provides tools for the triage, response, and remediation of incidents.
Users with at least Guest permissions can access incidents on public projects.
Create incidents manually
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:
- Go to your project Issues > List, and select New issue.
- In the Type dropdown, select Incident. Only fields relevant to incidents are displayed on the page.
- Create the incident as needed, and select Create issue to save the incident.
For users with at least Guest permissions, the Incident list is available at Issues > Lists 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
- Critical - S1
- High - S2
- Medium - S3
- Low - S4
- 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:
- Date created - How long ago the incident was created.
- Assignees - The user assigned to the incident.
- Published - Displays a green check mark () if the incident is published to a Status Page.
The Incident list displays incidents sorted by incident created date. 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.
Users with at least Guest permissions can view the Incident Details page. Navigate to Issues > List in your project’s sidebar, and select an incident from the list.
When you take any of these actions on an incident, WVS logs a system note and displays it in the Incident Details view:
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 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, WVS displays a summary that includes the following fields:
- Start time
- Monitoring tool
Comments are displayed in threads, but can be displayed chronologically by toggling on the recent updates view.
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.
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. Click the Add a to do button at the top of the right-hand side bar to add a to-do item.
Change incident status
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.
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.
For Additional Support please reach out to us on our Discord or by Email.