INA-8136: Add documentation for incident follow-ups #32443
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
Contributor
Preview links (active after the
|
Updated sections on defining and exporting incident follow-ups for clarity and accuracy.
Contributor
|
Thanks a bunch for drafting up this doc! I created a card for someone on our team to review in more detail. DOCS-12453 |
estherk15
approved these changes
Nov 3, 2025
content/en/service_management/incident_management/follow-ups.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/follow-ups.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/follow-ups.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Contributor
Author
|
@estherk15 Any idea why |
dussault-antoine
pushed a commit
that referenced
this pull request
Nov 13, 2025
* Add new follow-up documentation * Revise follow-ups management and export instructions Updated sections on defining and exporting incident follow-ups for clarity and accuracy. * Update content/en/service_management/incident_management/follow-ups.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> * Update content/en/service_management/incident_management/follow-ups.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> * Update content/en/service_management/incident_management/follow-ups.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> * Update content/en/service_management/incident_management/follow-ups.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> * Update content/en/service_management/incident_management/follow-ups.md Co-authored-by: Esther Kim <esther.kim@datadoghq.com> --------- Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
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.
What does this PR do? What is the motivation?
Adds new Incident Management documentation for follow-ups.
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