Update custom_schedules.md - #39856
Open
DavidGrashton wants to merge 2 commits into
Open
Conversation
Contributor
Preview links (active after the
|
estherk15
reviewed
Sep 11, 2026
estherk15
approved these changes
Sep 11, 2026
estherk15
left a comment
estherk15
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the update! Left one suggestion.
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Monitors with custom schedules have different group-retention times, which is not mentioned in the public docs. I confirmed with Alerting Product that this is okay to document. The info can be found in the internal docs here: https://datadoghq.atlassian.net/wiki/spaces/TS/pages/328435101/Troubleshooting+Monitor+Alerts#Monitor-Status-and-Groups
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Fed Claude my initial draft and worked with it to refine the wording and confirm formatting.
Additional notes