You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/service_management/incident_management/_index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,8 +54,8 @@ Incident Management requires no installation. Get started by taking a Learning C
54
54
{{< /whatsnext >}}
55
55
56
56
## View your incidents
57
-
To view your incidents, go to the [Incidents][1] page to see a feed of all ongoing incidents.
58
-
- Filter your incidents through the properties listed on the left, including Status, Severity, and Time To Repair (hours).
57
+
To view your incidents, go to the [Incidents][1] page to see a feed of all ongoing incidents.
58
+
- Filter your incidents through the properties listed on the left, including Status, Severity, and Time To Repair (hours).
59
59
- Use the Search field to enter tag attributes or keywords.
60
60
- Export your search results with the Export button at the top of the incident list.
61
61
- Configure additional fields that appear for all incidents in [Incident Settings][2].
@@ -68,8 +68,8 @@ You can also view your Incidents list from your mobile device home screen and ma
68
68
## Describing the incident
69
69
70
70
When declaring an incident, it is critical to provide a comprehensive description, detailing what happened, why it occurred, and related attributes to ensure all stakeholders in the incident management process are fully informed. The essential elements of an incident declaration include a title, severity level, incident commanders. Effective incident management documentation includes:
71
-
- Updating incident details, including its status, impact, root cause, detection methods, and service impacts.
72
-
- Forming and managing a response team, using custom responder roles, and leveraging metadata attributes for detailed incident assessment.
71
+
- Updating incident details, including its status, impact, root cause, detection methods, and service impacts.
72
+
- Forming and managing a response team, using custom responder roles, and leveraging metadata attributes for detailed incident assessment.
73
73
- Configuring notifications to keep all stakeholders informed throughout the incident resolution process.
74
74
75
75
For more information, see the [Describe an Incident][20] documentation.
@@ -91,7 +91,7 @@ Incident Management integrates closely with other Datadog products, including:
91
91
92
92
### Third-party integrations
93
93
94
-
In addition to integrating with [Slack][11] and [Microsoft Teams][23] for chat and video calls, Incident Management also integrates with:
94
+
Incident Management also has rich third-party integrations, including:
95
95
96
96
-[Atlassian Status Page][24] to create status pages connected to the incident.
97
97
-[Confluence][22] to generate incident postmortems.
0 commit comments