Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
7013cfb3
Commit
7013cfb3
authored
Jul 30, 2020
by
Amy Qualls
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'incident-list-documentation' into 'master'
Add incident docs Closes #231535 See merge request gitlab-org/gitlab!37879
parents
732ee4e4
bd28d73c
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
32 additions
and
1 deletion
+32
-1
doc/operations/incident_management/img/incident_list_13_3.png
...operations/incident_management/img/incident_list_13_3.png
+0
-0
doc/operations/incident_management/index.md
doc/operations/incident_management/index.md
+32
-1
No files found.
doc/operations/incident_management/img/incident_list_13_3.png
0 → 100644
View file @
7013cfb3
52.4 KB
doc/operations/incident_management/index.md
View file @
7013cfb3
...
@@ -7,7 +7,38 @@ info: To determine the technical writer assigned to the Stage/Group associated w
...
@@ -7,7 +7,38 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Incident management
# Incident management
GitLab offers solutions for handling incidents in your applications and services,
GitLab offers solutions for handling incidents in your applications and services,
such as setting up Prometheus alerts, displaying metrics, and sending notifications.
such as
[
setting up Prometheus alerts
](
#configure-prometheus-alerts
)
,
[
displaying metrics
](
#embed-metrics-in-incidents-and-issues
)
, and sending notifications.
While no configuration is required to use the
[
manual features
](
#create-an-incident-manually
)
of incident management, both automation and
[
configuration
](
#configure-incidents-ultimate
)
of incident management are only available in
[
GitLab Ultimate and GitLab.com Gold
](
https://about.gitlab.com/pricing/
)
.
For users with at least Developer
[
permissions
](
../../user/permissions.md
)
, the
Incident Management list is available at
**{cloud-gear}**
**Operations > Incidents**
in your project's sidebar. The list contains the following metrics:
![
Incident Management List
](
img/incident_list_13_3.png
)
-
**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.
NOTE:
**Note:**
Incidents share the
[
Issues API
](
../../user/project/issues/index.md
)
.
## Create an incident manually
> [Moved](https://gitlab.com/gitlab-org/monitor/health/-/issues/24) to GitLab core in 13.3.
To create a Incident you can take any of the following actions:
-
Navigate to
**{cloud-gear}**
**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 incidents **(ULTIMATE)**
## Configure incidents **(ULTIMATE)**
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment