This product is not supported for your selected
Datadog site. (
).
A Page is an alert that requires an on-call responder’s attention. Pages move through the following life cycle:
- Triggered: The Page has been sent, but no one has taken ownership. The escalation policy runs according to its configuration, notifying additional responders if no one responds within the defined time frame.
- Acknowledged: A responder has claimed the Page. Escalation notifications stop, and the responder begins working on the issue.
- Resolved: The underlying issue has been addressed, and the Page is closed.
This guide explains how to trigger, acknowledge, reassign, and resolve Pages.
Trigger a Page
A Page is sent to a Team and routed through its escalation policies and schedules. After your Team is onboarded to Datadog On-Call, you can start paging it.
Trigger Pages from monitors
Send a Page by mentioning a Team’s handle with oncall- prepended. For example, to send a Page to the Checkout Operations Team (@checkout-operations), mention @oncall-checkout-operations.
You can send Pages to On-Call Teams anywhere @-handles are supported, including monitors, Incident Management, security detection rules, and Event Management.
Resolving Pages automatically
When a monitor recovers, any Page it triggered is automatically set to Resolved if the recovery notification includes the On-Call Team mention (for example, @oncall-payments).
If the mention appears only in the alert template (for example, within {{#is_alert}} ... {{/is_alert}}) and not in the recovery message, the Page does not auto-resolve.
Monitors and dynamic urgencies
If you send a Page through a monitor alert and the Team’s routing rule uses dynamic urgencies:
- If the WARN threshold is crossed, the Page urgency is set to
low. - If the ALERT threshold is crossed, the Page urgency is set to
high.
Trigger Pages through email
Generate a unique email address to trigger a Page directly to a Team’s on-call responders. Emails sent to this address follow the Team’s configured routing and escalation policies.
Some teams embed this address in a human-readable distribution list (for example, page-network@company.com) to make it more recognizable.
To page a Team through email:
- Go to the Team’s page and scroll to Custom Triggering Sources.
- Under the email trigger section, click Generate.
Trigger Pages through incidents
Trigger a Page directly from an active incident to escalate and involve additional responders without leaving the workflow. See Trigger a Page from an incident for detailed instructions.
Trigger Pages through calls
Trigger a Page through Live Call Routing by calling a dedicated phone number.
Trigger Pages manually
Send a Page from the Datadog platform, or through a tool like Slack or Microsoft Teams. This lets you alert a Team or individual directly, even if they are not On-Call.
Through Datadog
- Go to On-Call > Teams.
- Find the Team you want to page. Select Page.
- Enter a Page title and add more context in the Description field. Select Page.
Pages sent manually through Datadog are always high urgency.
Through Slack
- Install the Datadog Slack app.
- Enter
/datadog page or /dd page. - Select a Team to send a Page to.
Pages sent from Slack are always high urgency.
To receive Page notifications in Slack, see Routing Rules.
Respond to a Page
Go to On-Call > Pages to view all active and historical Pages. Click a Page to open its side panel and take action, or select the checkbox next to one or more Pages to bulk-edit them.
Acknowledge a Page
Acknowledging a Page signals that you’re actively working on it and stops the escalation policy from notifying the next tier of responders. If you do not acknowledge the Page, escalation continues and additional responders may be paged.
To acknowledge a Page:
- Click the Page to open its side panel.
- Under Next Steps, select Acknowledge.
The Page status changes to Acknowledged.
Reassign a Page
Reassign a Page if it was routed to the wrong person or Team, or if you need to transfer ownership to someone better positioned to respond. When you reassign a Page, the Page history remains intact.
To reassign a Page:
Click the Page to open its side panel.
Under Next Steps, select Reassign. This opens a Reassign Page modal.
Select the user or Team to reassign to.
Optionally, add a comment explaining the handoff.
Click Reassign.
The new recipient is notified immediately.
Note: You can only reassign Pages with a Triggered or Acknowledged status.
Resolve a Page
Resolve a Page when the underlying issue is addressed. This closes the Page and sets its status to Resolved.
To resolve a Page:
- Click the Page to open its side panel.
- Under Next Steps, select Resolve.
If the Page was triggered by a monitor, it resolves automatically when the monitor recovers—provided the recovery notification includes the On-Call Team mention. See Trigger a Page for details.
Declare an incident from a Page
If a Page requires cross-team coordination, stakeholder communication, or formal tracking, promote it to an incident. This creates an incident in Incident Management with the Page context pre-filled.
To declare an incident:
Click the Page to open its side panel.
Under Next Steps, select Declare Incident.
Review and adjust the pre-filled details as needed.
Select Declare Incident to confirm.
For guidance on incident severity levels and responder roles, see Incident Management.
The Page timeline is an activity log that records when the Page was triggered, who was notified, and how escalation progressed. You can add your own comments to provide context for other responders.
Use comments to:
- Document what you’ve already investigated or ruled out
- Provide context when handing off to another responder
- Record external factors that affected your response
To add a comment, open the Page and enter your text in the Timeline section.
Further Reading
Additional helpful documentation, links, and articles:
