On-Call Integrations

This product is not supported for your selected Datadog site. ().

Overview

Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party monitoring, alerting, and incident management tools to send Pages directly to your On-Call Teams. Alerts from any part of your stack then reach the right responders through your configured escalation policies. For more information, see Trigger a Page.

Each native integration listed on this page includes setup instructions on its own integration tile. These instructions cover how to configure the third-party tool to send a Page. They also cover how to map its alerts to a Datadog On-Call Team. If your tool doesn’t have a native integration, use the generic webhook integration instead.

Available integrations

Datadog On-Call includes native paging support for the following tools:

Preview integrations

The following integrations are available as a Preview. Select a tile to request access.

Generic webhook integration

If your tool is not listed, use the Datadog Events API to trigger On-Call Pages from any source that can make an HTTP request.

Post an event with the following parameters:

ParameterValue
aggregation_keyA unique, user-defined identifier for the alert. Datadog uses this value for deduplication: If an incoming alert’s aggregation_key matches an already triggered Page, Datadog doesn’t create a Page. Datadog also uses this value to link a recovery event to its open Page.
categoryThe type of event. Set to alert to trigger a Page.
textThe body of the alert message. Include @oncall-<TEAM_HANDLE> to route the Page to the correct On-Call Team.
titleA short summary of the alert. Displayed as the Page’s title.

The @oncall-<TEAM_HANDLE> mention in text determines which On-Call Team receives the Page. Replace <TEAM_HANDLE> with your team’s handle as configured in Datadog.

{
  "data": {
    "attributes": {
      "aggregation_key": "alert_unique_identifier",
      "attributes": {
        "priority": "1",
        "status": "error"
      },
      "category": "alert",
      "message": "@oncall-database Something is broken!",
      "title": "High memory usage"
    },
    "type": "event"
  }
}

Further reading

Additional helpful documentation, links, and articles: