INA-7891: Update Incident Management landing page #30850
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR updates the Incident Management landing page (https://docs.datadoghq.com/service_management/incident_management/) to clarify the purpose of the Incident Management product and highlight new integrations that are available.
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
cperryk
force-pushed
the
christopher.kirk/update-incident-management-landing-page
branch
from
3c5c8fa to
61a9755
Compare
Preview links (active after the
|
cperryk
force-pushed
the
christopher.kirk/update-incident-management-landing-page
branch
from
61a9755 to
8075432
Compare
cperryk
force-pushed
the
christopher.kirk/update-incident-management-landing-page
branch
from
8075432 to
b8abf55
Compare
drichards-87
requested changes
Aug 1, 2025
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
…e' of github.com:DataDog/documentation into christopher.kirk/update-incident-management-landing-page
cperryk
changed the title
drichards-87
approved these changes
Aug 5, 2025
drichards-87
deleted the
christopher.kirk/update-incident-management-landing-page
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the Incident Management documentation landing page to clarify the functions of the Incident Management product and highlight new integrations that are available.
It also updates the analytics page to be clearer about what various analytical measures mean.
What does this PR do? What is the motivation?
This PR updates the language to more effectively explain the benefit of the Incident Management product across the identification, mitigation, resolution, and analysis stages of an incident.
We also have developed many new integrations since this was originally written, so this better highlights these capabilities.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes