Skip to content

Conversation

@Dalje-et
Copy link
Contributor

@Dalje-et Dalje-et commented Dec 3, 2025

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

  • Ready for merge

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

@Dalje-et Dalje-et requested a review from a team as a code owner December 3, 2025 13:19
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

Preview links (active after the build_preview check completes)

Modified Files

You can manually send a Page directly in the Datadog platform, or through a tool like Slack or Microsoft Teams. This lets you alert a Datadog team or an individual directly (even if they aren't On-Call).

### Reroute Pages
You can reroute an active Page to a different user or team if it is still open. Pages can only be rerouted when they’re in a Triggered or Acknowledged state, once a page is Resolved, it can’t be reassigned.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can reroute an active Page to a different user or team if it is still open. Pages can only be rerouted when they’re in a Triggered or Acknowledged state, once a page is Resolved, it can’t be reassigned.
You can reroute an active Page to a different user or team if it is still open. You can only reroute Pages that are Triggered or Acknowledged; you cannot reroute Pages that are Resolved.

To reroute a Page:

1. Open the active Page.
1. Click Reassign.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Click Reassign.
1. Click **Reassign**.

We bold UI strings

1. (Optional) Add a short message explaining the handoff.
1. Confirm the reroute.

The new recipient will be notified right away, and the page will continue from its current state.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The new recipient will be notified right away, and the page will continue from its current state.
The new recipient is notified immediately, and the Page continues from its current state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants