Skip to content

Commit 3c5c8fa

Browse files
committed
Remove redundant language on Incident Management homepage
1 parent 3f98808 commit 3c5c8fa

File tree

1 file changed

+5
-5
lines changed
  • content/en/service_management/incident_management

1 file changed

+5
-5
lines changed

content/en/service_management/incident_management/_index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ Incident Management requires no installation. Get started by taking a Learning C
5454
{{< /whatsnext >}}
5555

5656
## 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).
5959
- Use the Search field to enter tag attributes or keywords.
6060
- Export your search results with the Export button at the top of the incident list.
6161
- 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
6868
## Describing the incident
6969

7070
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.
7373
- Configuring notifications to keep all stakeholders informed throughout the incident resolution process.
7474

7575
For more information, see the [Describe an Incident][20] documentation.
@@ -91,7 +91,7 @@ Incident Management integrates closely with other Datadog products, including:
9191

9292
### Third-party integrations
9393

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:
9595

9696
- [Atlassian Status Page][24] to create status pages connected to the incident.
9797
- [Confluence][22] to generate incident postmortems.

0 commit comments

Comments
 (0)