[error-tracking] Improve monitor documentation #28452
Conversation
Preview links (active after the
|
estherk15
left a comment
estherk15
left a comment
There was a problem hiding this comment.
Thanks for making those updates! Left some suggestions for clarity and formatting, reach out if you have any questions!
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>
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>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
estherk15
left a comment
estherk15
left a comment
There was a problem hiding this comment.
Thanks for making those updates, this looks great!
Thank you for the suggestions, some I noticed looked a bit odd (namely bold/subtitle differences) but not an expert in doc formatting. Your changes definitely make it a whole lot better :) |
iadjivon
left a comment
iadjivon
left a comment
There was a problem hiding this comment.
Thanks Esther! Approved on my end as well, Gillaume
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-mergequeue
bot
deleted the
guillaume.barrier/ERRORT-5060-improve-et-monitors-doc
branch
What does this PR do? What is the motivation?
Update the public documentation for Error Tracking monitors.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in 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.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes