Open
Conversation
Extends the on-call routing rules documentation with comprehensive coverage of the support hours feature, including: - New support hours section with overview and workflow explanation - Comparison table distinguishing support hours from time restrictions - Configuration guide with time zone and restriction window setup - Two practical examples (business hours, split shift coverage) - Updated best practices for protecting responders - Cross-reference in on-call overview page The support hours feature allows teams to snooze escalation policy notifications outside defined time windows while still creating Pages immediately for tracking purposes. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Avoid conflating support hours behavior with the upcoming Snooze feature. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Reorganizes the on-call routing rules documentation to lead with a step-by-step procedure, making it easier for users to get started. Changes include: - New "Create a routing rule" procedure section with screenshots - Routing rule syntax and support hours moved to subsections - Routing rule examples and best practices updated to cover support hours - Support hours examples clarified to note the hold toggle assumption - Editorial fixes: toggle ambiguity, Teams/Slack parity, Dynamic urgency example Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
1 task
domalessi
commented
Feb 24, 2026
domalessi
commented
Feb 24, 2026
domalessi
added
editorial review
Contributor
Author
|
Editorial review card: https://datadoghq.atlassian.net/browse/DOCS-13497 |
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?
This PR restructures the Routing Rules page and adds content for "support hours" (folded in from #34589). I also did a light clean up of some of the existing content.
Specific changes:
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