Add investigate and timeline page #25889
Merged
Conversation
This file contains 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
github-actions
bot
added
Architecture
neko-dd
reviewed
Oct 24, 2024
content/en/service_management/incident_management/investigate/_index.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/_index.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/_index.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/_index.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/_index.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/timeline.md
Outdated
Show resolved
Hide resolved
|
|
||
| | Content type | Description | | ||
| | ------------------ | ------------------------------------------------------------------------------------------------------ | | ||
| | Responder note | A note manually written by an incident responder. Responder notes have the following sub-types:<br>- *Graph*: The responder note contains one or more Datadog graphs<br>- *Link*: The responder note contains a hyperlink<br>- *Code*: The responder note contains text wrapped in Markdown syntax for code blocks |
There was a problem hiding this comment.
Does a responder note always have to be of one of the subtypes, or is there just a "plain" responder note type?
There was a problem hiding this comment.
You can have a plain note, within a note cell you can add graphs and links. If you don't add anything, it'd just be a responder note.
content/en/service_management/incident_management/investigate/timeline.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/timeline.md
Outdated
Show resolved
Hide resolved
content/en/service_management/incident_management/investigate/timeline.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Sandra (neko) <[email protected]>
neko-dd
approved these changes
Oct 25, 2024
|
/merge |
|
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
theraffoul
pushed a commit
that referenced
this pull request
Nov 25, 2024
* Add investigate and timeline page * Apply suggestions from code review Co-authored-by: Sandra (neko) <[email protected]> * Add Timeline docs referenc * Add reference link number --------- Co-authored-by: Sandra (neko) <[email protected]>
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?
This reorganize the Incident details page
Merge instructions
Additional notes