From 911260e91a255ed955b92647bbeea25f57919432 Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Mon, 8 Jun 2026 12:15:28 +0200 Subject: [PATCH 01/15] Adding integration page in On-Call --- .../incident_response/on-call/integrations.md | 175 ++++++++++++++++++ 1 file changed, 175 insertions(+) create mode 100644 content/en/incident_response/on-call/integrations.md diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md new file mode 100644 index 00000000000..2735a7db1ba --- /dev/null +++ b/content/en/incident_response/on-call/integrations.md @@ -0,0 +1,175 @@ +--- +title: On-Call Integrations +further_reading: +- link: '/incident_response/on-call/' + tag: 'Documentation' + text: 'Datadog On-Call' +- link: '/incident_response/on-call/pages/' + tag: 'Documentation' + text: 'Pages' +- link: '/incident_response/on-call/routing_rules/' + tag: 'Documentation' + text: 'Routing Rules' +--- + +## Overview + +Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party tools to send Pages directly to your On-Call teams, so alerts from any part of your stack reach the right responders through your configured escalation policies. + +## Slack + +Use the Datadog Slack app to manage On-Call operations directly from Slack. + +### Prerequisites + +- The [Datadog Slack app][1] installed in your Slack workspace +- On-Call enabled for your Datadog organization + +### Trigger a Page from Slack + +Run the following slash command in any Slack channel: + +``` +/dd page +``` + +Select the team to page and provide a title and description for the Page. + +Pages sent from Slack are always `high` urgency. + +## Prometheus Alertmanager + +Route Prometheus alerts to Datadog On-Call through Alertmanager's webhook receiver. + +### Prerequisites + +- A running Prometheus and Alertmanager setup +- A Datadog API key + +### Setup + +Edit your `alertmanager.yml` to add a Datadog webhook receiver. Set `group_by` to `['alertname']` so Alertmanager sends one alert per payload, as the Datadog endpoint accepts only one event at a time. + +```yaml +receivers: +- name: datadog-oncall + webhook_configs: + - send_resolved: true + url: 'https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=prometheus&oncall_team=' +route: + group_by: ['alertname'] + group_wait: 10s + group_interval: 5m + receiver: datadog-oncall + repeat_interval: 3h +``` + +Replace `` with your Datadog API key and `` with your On-Call team handle. + +Restart your services after saving the configuration: + +```shell +sudo systemctl restart prometheus.service alertmanager.service +``` + +### How it works + +When Alertmanager fires an alert, it sends a POST request to the Datadog event intake endpoint. Datadog routes the resulting event to the specified On-Call team based on the `oncall_team` parameter. + +Setting `send_resolved: true` ensures Alertmanager notifies Datadog when alerts clear, which automatically resolves the corresponding Page. Resolved notifications may be delayed until the next `group_interval`. + +To route different alerts to different On-Call teams, define multiple receivers with different `oncall_team` values and use `matchers` in your route configuration to direct alerts accordingly. + +## Pingdom + +Route Pingdom uptime check alerts to Datadog On-Call through a webhook integration. + +### Prerequisites + +- A Pingdom account with at least one configured uptime check +- A Datadog API key + +### Setup + +1. In Pingdom, go to [**Integrations > Integrations**][2]. +1. Click **Add new**. +1. Enter a name for the integration. +1. In the **URL** field, enter the following webhook URL: + ``` + https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=pingdom-v3&oncall_team= + ``` + Replace `` with your Datadog API key and `` with your On-Call team handle. +1. Click **Save integration**. + +After saving, enable the integration on your uptime checks: + +1. Go to [**Monitoring > Uptime**][3]. +1. Open the check you want to configure. +1. Select the checkbox next to the integration you created. + +### How it works + +When a Pingdom check changes status (for example, from up to down), Pingdom sends a POST request to the configured webhook URL. Datadog routes the resulting event to the specified On-Call team. When the check recovers, Pingdom sends a resolved notification that automatically closes the Page. + +## Sentry + +Route Sentry alerts to Datadog On-Call through an internal integration and webhook forwarder. + +### Prerequisites + +- Sentry admin access to create internal integrations +- A deployed webhook forwarder service (Sentry does not support custom headers on webhook requests, so an intermediate service is required to inject the Datadog API key) +- A Datadog API key + +### Setup + +#### Step 1: Deploy a webhook forwarder + +Deploy an intermediate service that: +- Receives POST requests from Sentry +- Injects the required Datadog API key as a query parameter +- Forwards the payload to the following Datadog endpoint: + ``` + https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=sentry&oncall_team= + ``` + +Replace `` with your Datadog API key and `` with your On-Call team handle. + +#### Step 2: Create a Sentry internal integration + +1. In Sentry, go to **Settings > Developer Settings > Internal Integrations**. +1. Click **Create New Integration**. +1. Enter a name (for example, `Datadog On-Call`). +1. Set the **Webhook URL** to your forwarder's public URL. +1. Enable **Alert Rule Action**. +1. Set the following permissions: + - **Issue & Event**: Read + - **Alerts**: Read +1. Enable webhooks for `issue` and `error` event types. +1. Save the integration. + +#### Step 3: Configure an alert rule + +1. In your Sentry project, go to **Settings > Alerts > Issue Alerts**. +1. Create or edit an alert rule. +1. Add the action **Send a notification using your internal integration** and select the integration you created. +1. Click **Send Test Notification** to confirm delivery. + +### How it works + +When Sentry fires an alert, it sends a POST request to your forwarder, which relays it to the Datadog event intake endpoint. Datadog routes the resulting event to the specified On-Call team. + +The aggregation key used to correlate and resolve events depends on the event type: + +| Event type | Aggregation key | +|------------|-----------------| +| Error events | Issue ID parsed from `data.error.issue_url` (the URL path segment after `issues/`) | +| Issue events | `data.issue.id` (truncated to 100 characters; MD5-hashed if over the limit) | + +## Further Reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: /integrations/slack/?tab=datadogforslack +[2]: https://my.pingdom.com/integrations/settings +[3]: https://my.pingdom.com/newchecks/checks From 388dca52446756b60c07dc9bf30797728225f048 Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Mon, 8 Jun 2026 13:56:29 +0200 Subject: [PATCH 02/15] Update On-Call integrations page to use collapsible sections --- .../incident_response/on-call/integrations.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 2735a7db1ba..44978427f03 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -16,8 +16,19 @@ further_reading: Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party tools to send Pages directly to your On-Call teams, so alerts from any part of your stack reach the right responders through your configured escalation policies. +The following integrations are supported: + +| Integration | Trigger method | +|-------------|---------------| +| [Slack](#slack) | Slash command | +| [Prometheus Alertmanager](#prometheus-alertmanager) | Webhook | +| [Pingdom](#pingdom) | Webhook | +| [Sentry](#sentry) | Webhook (with forwarder) | + ## Slack +{{% collapse-content title="Set up the Slack integration" level="h3" %}} + Use the Datadog Slack app to manage On-Call operations directly from Slack. ### Prerequisites @@ -37,8 +48,12 @@ Select the team to page and provide a title and description for the Page. Pages sent from Slack are always `high` urgency. +{{% /collapse-content %}} + ## Prometheus Alertmanager +{{% collapse-content title="Set up the Prometheus Alertmanager integration" level="h3" %}} + Route Prometheus alerts to Datadog On-Call through Alertmanager's webhook receiver. ### Prerequisites @@ -80,8 +95,12 @@ Setting `send_resolved: true` ensures Alertmanager notifies Datadog when alerts To route different alerts to different On-Call teams, define multiple receivers with different `oncall_team` values and use `matchers` in your route configuration to direct alerts accordingly. +{{% /collapse-content %}} + ## Pingdom +{{% collapse-content title="Set up the Pingdom integration" level="h3" %}} + Route Pingdom uptime check alerts to Datadog On-Call through a webhook integration. ### Prerequisites @@ -111,8 +130,12 @@ After saving, enable the integration on your uptime checks: When a Pingdom check changes status (for example, from up to down), Pingdom sends a POST request to the configured webhook URL. Datadog routes the resulting event to the specified On-Call team. When the check recovers, Pingdom sends a resolved notification that automatically closes the Page. +{{% /collapse-content %}} + ## Sentry +{{% collapse-content title="Set up the Sentry integration" level="h3" %}} + Route Sentry alerts to Datadog On-Call through an internal integration and webhook forwarder. ### Prerequisites @@ -166,6 +189,8 @@ The aggregation key used to correlate and resolve events depends on the event ty | Error events | Issue ID parsed from `data.error.issue_url` (the URL path segment after `issues/`) | | Issue events | `data.issue.id` (truncated to 100 characters; MD5-hashed if over the limit) | +{{% /collapse-content %}} + ## Further Reading {{< partial name="whats-next/whats-next.html" >}} From 7e430bdb34a00599e726dba79f229cbdab7d103d Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 13:53:01 +0200 Subject: [PATCH 03/15] Add Sentry forwarder setup link in integrations page --- content/en/incident_response/on-call/integrations.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 44978427f03..acdf70503cc 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -158,6 +158,8 @@ Deploy an intermediate service that: Replace `` with your Datadog API key and `` with your On-Call team handle. +For detailed forwarder setup instructions, see the [Sentry integration docs][4]. + #### Step 2: Create a Sentry internal integration 1. In Sentry, go to **Settings > Developer Settings > Internal Integrations**. @@ -198,3 +200,4 @@ The aggregation key used to correlate and resolve events depends on the event ty [1]: /integrations/slack/?tab=datadogforslack [2]: https://my.pingdom.com/integrations/settings [3]: https://my.pingdom.com/newchecks/checks +[4]: /integrations/sentry/#step-1-deploy-the-webhook-forwarder From 8218f97a05f8d7ec4cdb6190b9252b724fa73afb Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 14:04:51 +0200 Subject: [PATCH 04/15] Add Amazon CloudWatch and Azure Monitor integrations --- .../incident_response/on-call/integrations.md | 70 +++++++++++++++++++ 1 file changed, 70 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index acdf70503cc..18388ab9d6c 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -24,6 +24,8 @@ The following integrations are supported: | [Prometheus Alertmanager](#prometheus-alertmanager) | Webhook | | [Pingdom](#pingdom) | Webhook | | [Sentry](#sentry) | Webhook (with forwarder) | +| [Amazon CloudWatch](#amazon-cloudwatch) | SNS webhook | +| [Azure Monitor](#azure-monitor) | Webhook | ## Slack @@ -193,6 +195,70 @@ The aggregation key used to correlate and resolve events depends on the event ty {{% /collapse-content %}} +## Amazon CloudWatch + +{{% collapse-content title="Set up the Amazon CloudWatch integration" level="h3" %}} + +Route Amazon CloudWatch alarms to Datadog On-Call through Amazon SNS. + +### Prerequisites + +- The [Amazon Web Services integration][5] configured in Datadog +- A Datadog API key + +### Setup + +1. In AWS, create an SNS topic (for example, `datadog-oncall-alerts`). +1. Add an HTTPS subscription to the topic using the following webhook URL: + ``` + https://app.datadoghq.com/intake/webhook/sns?api_key=&oncall_team= + ``` + Replace `` with your Datadog API key and `` with your On-Call team handle. +1. In CloudWatch, open the alarm you want to route to On-Call. +1. Under **Notification**, set the **In alarm** action to send a notification to the SNS topic you created. + +### How it works + +When a CloudWatch alarm enters the **In alarm** state, it publishes a message to the SNS topic. SNS delivers the message to Datadog, which creates a Page and routes it to the specified On-Call team. When the alarm recovers, SNS sends a resolution notification that automatically closes the Page. + +To route alarms from different services or teams, create one SNS topic per team, each with its own Datadog subscription URL using a different `oncall_team` value. + +For more details, see the [Amazon SNS integration docs][6]. + +{{% /collapse-content %}} + +## Azure Monitor + +{{% collapse-content title="Set up the Azure Monitor integration" level="h3" %}} + +Route Azure Monitor alerts to Datadog On-Call through an Azure Action Group webhook. + +### Prerequisites + +- Access to the Azure Portal with permissions to manage Monitor alerts and Action Groups +- A Datadog API key + +### Setup + +1. In Azure Portal, go to **Monitor > Alerts > Action Groups**. +1. Create or edit an Action Group and add a **Webhook** action with the following URL: + ``` + https://event-management-intake.datadoghq.com/api/v2/events/webhook?integration_id=azure-monitor-alerts&dd-api-key=&oncall_team= + ``` + Replace `` with your Datadog API key and `` with your On-Call team handle. For non-US1 sites, replace `event-management-intake.datadoghq.com` with the endpoint for your [Datadog site][7]. +1. Enable **Common Alert Schema** on the webhook action. This is required for Datadog to parse the payload correctly. +1. Attach the Action Group to your alert rules by editing each rule and selecting the Action Group under **Actions**. + +**Note**: Do not use the Azure built-in test button to verify the integration. It sends payloads with outdated timestamps that Datadog rejects. Use a real test alert instead. + +### How it works + +When an Azure Monitor alert fires, Azure sends a POST request to the configured webhook URL. Datadog routes the resulting event to the specified On-Call team. When the alert resolves, Azure sends a resolution notification that automatically closes the Page. + +For more details, see the [Azure Monitor Alerts integration docs][8]. + +{{% /collapse-content %}} + ## Further Reading {{< partial name="whats-next/whats-next.html" >}} @@ -201,3 +267,7 @@ The aggregation key used to correlate and resolve events depends on the event ty [2]: https://my.pingdom.com/integrations/settings [3]: https://my.pingdom.com/newchecks/checks [4]: /integrations/sentry/#step-1-deploy-the-webhook-forwarder +[5]: /integrations/amazon_web_services/ +[6]: /integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns +[7]: /getting_started/site/ +[8]: /integrations/azure-monitor-alerts/ From 14427cbb2475ad5ae81ceb15dd4bcead4166a5e1 Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 15:49:46 +0200 Subject: [PATCH 05/15] Add integrations page to On-Call sidebar navigation --- config/_default/menus/main.en.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 69ba6d57d55..3436f8b89fc 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2816,11 +2816,16 @@ menu: parent: oncall identifier: oncall_profile_settings weight: 7 + - name: Integrations + url: incident_response/on-call/integrations/ + parent: oncall + identifier: oncall_integrations + weight: 8 - name: Guides url: incident_response/on-call/guides/ parent: oncall identifier: oncall_guides - weight: 8 + weight: 9 - name: Status Pages url: incident_response/status_pages/ pre: status-page-wui From e07dc34f93373e71c754ce3448e36991bc08324e Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 16:44:25 +0200 Subject: [PATCH 06/15] Restructure On-Call integrations page to card grid layout --- .../incident_response/on-call/integrations.md | 259 +----------------- 1 file changed, 8 insertions(+), 251 deletions(-) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 18388ab9d6c..6852dd4ccc2 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -16,258 +16,15 @@ further_reading: Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party tools to send Pages directly to your On-Call teams, so alerts from any part of your stack reach the right responders through your configured escalation policies. -The following integrations are supported: - -| Integration | Trigger method | -|-------------|---------------| -| [Slack](#slack) | Slash command | -| [Prometheus Alertmanager](#prometheus-alertmanager) | Webhook | -| [Pingdom](#pingdom) | Webhook | -| [Sentry](#sentry) | Webhook (with forwarder) | -| [Amazon CloudWatch](#amazon-cloudwatch) | SNS webhook | -| [Azure Monitor](#azure-monitor) | Webhook | - -## Slack - -{{% collapse-content title="Set up the Slack integration" level="h3" %}} - -Use the Datadog Slack app to manage On-Call operations directly from Slack. - -### Prerequisites - -- The [Datadog Slack app][1] installed in your Slack workspace -- On-Call enabled for your Datadog organization - -### Trigger a Page from Slack - -Run the following slash command in any Slack channel: - -``` -/dd page -``` - -Select the team to page and provide a title and description for the Page. - -Pages sent from Slack are always `high` urgency. - -{{% /collapse-content %}} - -## Prometheus Alertmanager - -{{% collapse-content title="Set up the Prometheus Alertmanager integration" level="h3" %}} - -Route Prometheus alerts to Datadog On-Call through Alertmanager's webhook receiver. - -### Prerequisites - -- A running Prometheus and Alertmanager setup -- A Datadog API key - -### Setup - -Edit your `alertmanager.yml` to add a Datadog webhook receiver. Set `group_by` to `['alertname']` so Alertmanager sends one alert per payload, as the Datadog endpoint accepts only one event at a time. - -```yaml -receivers: -- name: datadog-oncall - webhook_configs: - - send_resolved: true - url: 'https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=prometheus&oncall_team=' -route: - group_by: ['alertname'] - group_wait: 10s - group_interval: 5m - receiver: datadog-oncall - repeat_interval: 3h -``` - -Replace `` with your Datadog API key and `` with your On-Call team handle. - -Restart your services after saving the configuration: - -```shell -sudo systemctl restart prometheus.service alertmanager.service -``` - -### How it works - -When Alertmanager fires an alert, it sends a POST request to the Datadog event intake endpoint. Datadog routes the resulting event to the specified On-Call team based on the `oncall_team` parameter. - -Setting `send_resolved: true` ensures Alertmanager notifies Datadog when alerts clear, which automatically resolves the corresponding Page. Resolved notifications may be delayed until the next `group_interval`. - -To route different alerts to different On-Call teams, define multiple receivers with different `oncall_team` values and use `matchers` in your route configuration to direct alerts accordingly. - -{{% /collapse-content %}} - -## Pingdom - -{{% collapse-content title="Set up the Pingdom integration" level="h3" %}} - -Route Pingdom uptime check alerts to Datadog On-Call through a webhook integration. - -### Prerequisites - -- A Pingdom account with at least one configured uptime check -- A Datadog API key - -### Setup - -1. In Pingdom, go to [**Integrations > Integrations**][2]. -1. Click **Add new**. -1. Enter a name for the integration. -1. In the **URL** field, enter the following webhook URL: - ``` - https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=pingdom-v3&oncall_team= - ``` - Replace `` with your Datadog API key and `` with your On-Call team handle. -1. Click **Save integration**. - -After saving, enable the integration on your uptime checks: - -1. Go to [**Monitoring > Uptime**][3]. -1. Open the check you want to configure. -1. Select the checkbox next to the integration you created. - -### How it works - -When a Pingdom check changes status (for example, from up to down), Pingdom sends a POST request to the configured webhook URL. Datadog routes the resulting event to the specified On-Call team. When the check recovers, Pingdom sends a resolved notification that automatically closes the Page. - -{{% /collapse-content %}} - -## Sentry - -{{% collapse-content title="Set up the Sentry integration" level="h3" %}} - -Route Sentry alerts to Datadog On-Call through an internal integration and webhook forwarder. - -### Prerequisites - -- Sentry admin access to create internal integrations -- A deployed webhook forwarder service (Sentry does not support custom headers on webhook requests, so an intermediate service is required to inject the Datadog API key) -- A Datadog API key - -### Setup - -#### Step 1: Deploy a webhook forwarder - -Deploy an intermediate service that: -- Receives POST requests from Sentry -- Injects the required Datadog API key as a query parameter -- Forwards the payload to the following Datadog endpoint: - ``` - https://event-management-intake.datadoghq.com/api/v2/events/webhook?dd-api-key=&integration_id=sentry&oncall_team= - ``` - -Replace `` with your Datadog API key and `` with your On-Call team handle. - -For detailed forwarder setup instructions, see the [Sentry integration docs][4]. - -#### Step 2: Create a Sentry internal integration - -1. In Sentry, go to **Settings > Developer Settings > Internal Integrations**. -1. Click **Create New Integration**. -1. Enter a name (for example, `Datadog On-Call`). -1. Set the **Webhook URL** to your forwarder's public URL. -1. Enable **Alert Rule Action**. -1. Set the following permissions: - - **Issue & Event**: Read - - **Alerts**: Read -1. Enable webhooks for `issue` and `error` event types. -1. Save the integration. - -#### Step 3: Configure an alert rule - -1. In your Sentry project, go to **Settings > Alerts > Issue Alerts**. -1. Create or edit an alert rule. -1. Add the action **Send a notification using your internal integration** and select the integration you created. -1. Click **Send Test Notification** to confirm delivery. - -### How it works - -When Sentry fires an alert, it sends a POST request to your forwarder, which relays it to the Datadog event intake endpoint. Datadog routes the resulting event to the specified On-Call team. - -The aggregation key used to correlate and resolve events depends on the event type: - -| Event type | Aggregation key | -|------------|-----------------| -| Error events | Issue ID parsed from `data.error.issue_url` (the URL path segment after `issues/`) | -| Issue events | `data.issue.id` (truncated to 100 characters; MD5-hashed if over the limit) | - -{{% /collapse-content %}} - -## Amazon CloudWatch - -{{% collapse-content title="Set up the Amazon CloudWatch integration" level="h3" %}} - -Route Amazon CloudWatch alarms to Datadog On-Call through Amazon SNS. - -### Prerequisites - -- The [Amazon Web Services integration][5] configured in Datadog -- A Datadog API key - -### Setup - -1. In AWS, create an SNS topic (for example, `datadog-oncall-alerts`). -1. Add an HTTPS subscription to the topic using the following webhook URL: - ``` - https://app.datadoghq.com/intake/webhook/sns?api_key=&oncall_team= - ``` - Replace `` with your Datadog API key and `` with your On-Call team handle. -1. In CloudWatch, open the alarm you want to route to On-Call. -1. Under **Notification**, set the **In alarm** action to send a notification to the SNS topic you created. - -### How it works - -When a CloudWatch alarm enters the **In alarm** state, it publishes a message to the SNS topic. SNS delivers the message to Datadog, which creates a Page and routes it to the specified On-Call team. When the alarm recovers, SNS sends a resolution notification that automatically closes the Page. - -To route alarms from different services or teams, create one SNS topic per team, each with its own Datadog subscription URL using a different `oncall_team` value. - -For more details, see the [Amazon SNS integration docs][6]. - -{{% /collapse-content %}} - -## Azure Monitor - -{{% collapse-content title="Set up the Azure Monitor integration" level="h3" %}} - -Route Azure Monitor alerts to Datadog On-Call through an Azure Action Group webhook. - -### Prerequisites - -- Access to the Azure Portal with permissions to manage Monitor alerts and Action Groups -- A Datadog API key - -### Setup - -1. In Azure Portal, go to **Monitor > Alerts > Action Groups**. -1. Create or edit an Action Group and add a **Webhook** action with the following URL: - ``` - https://event-management-intake.datadoghq.com/api/v2/events/webhook?integration_id=azure-monitor-alerts&dd-api-key=&oncall_team= - ``` - Replace `` with your Datadog API key and `` with your On-Call team handle. For non-US1 sites, replace `event-management-intake.datadoghq.com` with the endpoint for your [Datadog site][7]. -1. Enable **Common Alert Schema** on the webhook action. This is required for Datadog to parse the payload correctly. -1. Attach the Action Group to your alert rules by editing each rule and selecting the Action Group under **Actions**. - -**Note**: Do not use the Azure built-in test button to verify the integration. It sends payloads with outdated timestamps that Datadog rejects. Use a real test alert instead. - -### How it works - -When an Azure Monitor alert fires, Azure sends a POST request to the configured webhook URL. Datadog routes the resulting event to the specified On-Call team. When the alert resolves, Azure sends a resolution notification that automatically closes the Page. - -For more details, see the [Azure Monitor Alerts integration docs][8]. - -{{% /collapse-content %}} +{{< card-grid card_width="200px" >}} + {{< image-card href="/incident_response/on-call/pages/#through-slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} + {{< image-card href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} + {{< image-card href="/integrations/pingdom/" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} + {{< image-card href="/integrations/sentry/#setup" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} + {{< image-card href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} + {{< image-card href="/integrations/azure-monitor-alerts/" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} +{{< /card-grid >}} ## Further Reading {{< partial name="whats-next/whats-next.html" >}} - -[1]: /integrations/slack/?tab=datadogforslack -[2]: https://my.pingdom.com/integrations/settings -[3]: https://my.pingdom.com/newchecks/checks -[4]: /integrations/sentry/#step-1-deploy-the-webhook-forwarder -[5]: /integrations/amazon_web_services/ -[6]: /integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns -[7]: /getting_started/site/ -[8]: /integrations/azure-monitor-alerts/ From 7a44ec784f2fb8082ff304621f7cc2e42289622a Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 17:29:03 +0200 Subject: [PATCH 07/15] Update integration card links to point to On-Call sections --- content/en/incident_response/on-call/integrations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 6852dd4ccc2..4ef05df0de7 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -19,10 +19,10 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< card-grid card_width="200px" >}} {{< image-card href="/incident_response/on-call/pages/#through-slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} {{< image-card href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} - {{< image-card href="/integrations/pingdom/" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} - {{< image-card href="/integrations/sentry/#setup" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} + {{< image-card href="/integrations/pingdom/#page-a-datadog-on-call-team" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} + {{< image-card href="/integrations/sentry/#page-a-datadog-on-call-team" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} {{< image-card href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} - {{< image-card href="/integrations/azure-monitor-alerts/" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} + {{< image-card href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} {{< /card-grid >}} ## Further Reading From f20390b27c1c2b7809e14b0050675ec1d4ed0292 Mon Sep 17 00:00:00 2001 From: SimoneT-DD <132372485+SimoneT-DD@users.noreply.github.com> Date: Fri, 12 Jun 2026 17:59:46 +0200 Subject: [PATCH 08/15] Add Microsoft Teams integration to On-Call integrations page and pages doc --- content/en/incident_response/on-call/integrations.md | 1 + content/en/incident_response/on-call/pages/_index.md | 9 +++++++++ 2 files changed, 10 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 4ef05df0de7..8374077f7b2 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -18,6 +18,7 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< card-grid card_width="200px" >}} {{< image-card href="/incident_response/on-call/pages/#through-slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} + {{< image-card href="/incident_response/on-call/pages/#through-microsoft-teams" src="integrations_logos/microsoft_teams.png" alt="Microsoft Teams" title="Microsoft Teams" >}} {{< image-card href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} {{< image-card href="/integrations/pingdom/#page-a-datadog-on-call-team" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} {{< image-card href="/integrations/sentry/#page-a-datadog-on-call-team" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} diff --git a/content/en/incident_response/on-call/pages/_index.md b/content/en/incident_response/on-call/pages/_index.md index 39ad1c8a8d6..8d738f669b9 100644 --- a/content/en/incident_response/on-call/pages/_index.md +++ b/content/en/incident_response/on-call/pages/_index.md @@ -95,6 +95,14 @@ Pages sent from Slack are always `high` urgency. To receive Page notifications in Slack, see [Routing Rules][4]. +#### Through Microsoft Teams + +1. Install the [Datadog Microsoft Teams app][9]. +1. In any channel or chat, enter `@Datadog page`. +1. Select a Team to send a Page to. + +Pages sent from Microsoft Teams are always `high` urgency. + ## Respond to a Page Go to [**On-Call** > **Pages**][7] 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. @@ -185,3 +193,4 @@ To add a comment, open the Page and enter your text in the **Timeline** section. [6]: /incident_response/incident_management/ [7]: https://app.datadoghq.com/on-call/pages [8]: /monitors/notify/#renotify +[9]: /integrations/microsoft-teams/ From 887dac3a0e81a6368df84ef993faecb9e3b4c2b5 Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Mon, 22 Jun 2026 12:43:46 +0200 Subject: [PATCH 09/15] Add Zabbix integration to On-Call integrations grid Co-Authored-By: Claude Sonnet 4.6 --- content/en/incident_response/on-call/integrations.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 8374077f7b2..ff682df55e4 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -24,6 +24,7 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< image-card href="/integrations/sentry/#page-a-datadog-on-call-team" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} {{< image-card href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} {{< image-card href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} + {{< image-card href="/integrations/zabbix/#trigger-on-call-pages" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} {{< /card-grid >}} ## Further Reading From 538033cc87e740c530798ce5832262d4b7a80c15 Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Tue, 23 Jun 2026 13:40:40 +0200 Subject: [PATCH 10/15] Add Nagios integration tile and Events API fallback section to On-Call integrations page Co-Authored-By: Claude Sonnet 4.6 --- .../incident_response/on-call/integrations.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index ff682df55e4..5f494a14103 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -25,8 +25,26 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< image-card href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} {{< image-card href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} {{< image-card href="/integrations/zabbix/#trigger-on-call-pages" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} + {{< image-card href="/integrations/nagios/?tab=host#trigger-on-call-pages" src="integrations_logos/nagios.png" alt="Nagios" title="Nagios" >}} {{< /card-grid >}} +## Other tools + +If your tool is not listed above, use the [Datadog Events API][1] to trigger On-Call pages from any source that can make an HTTP request. + +Post an event with the following parameters: + +| Parameter | Value | +|-----------|-------| +| `alert_type` | `error` | +| `aggregation_key` | A string that groups related alerts into a single Page. | +| `title` | A short description of the alert. | +| `text` | Include `@oncall-` to route the Page to the correct On-Call team. | + +The `@oncall-` mention in `text` determines which On-Call team receives the Page. Replace `` with your team's handle as configured in Datadog. + +[1]: https://docs.datadoghq.com/api/latest/events/post-an-event/ + ## Further Reading {{< partial name="whats-next/whats-next.html" >}} From 0e88e222f3db14224d46e10a8535b3075b94fcd4 Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Wed, 24 Jun 2026 12:43:01 +0200 Subject: [PATCH 11/15] Add Catchpoint integration tile to On-Call integrations page Co-Authored-By: Claude Sonnet 4.6 --- content/en/incident_response/on-call/integrations.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 5f494a14103..dbd8a6b7490 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -26,6 +26,7 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< image-card href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} {{< image-card href="/integrations/zabbix/#trigger-on-call-pages" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} {{< image-card href="/integrations/nagios/?tab=host#trigger-on-call-pages" src="integrations_logos/nagios.png" alt="Nagios" title="Nagios" >}} + {{< image-card href="/integrations/catchpoint/#events" src="integrations_logos/catchpoint.png" alt="Catchpoint" title="Catchpoint" >}} {{< /card-grid >}} ## Other tools From 59ae1156cb471af87991eaee0fa39f7d8f991827 Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Fri, 3 Jul 2026 16:45:03 +0200 Subject: [PATCH 12/15] add integrations in preview --- .../en/incident_response/on-call/integrations.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index dbd8a6b7490..66e0eab66ca 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -29,6 +29,22 @@ Datadog On-Call supports multiple triggering sources beyond native Datadog monit {{< image-card href="/integrations/catchpoint/#events" src="integrations_logos/catchpoint.png" alt="Catchpoint" title="Catchpoint" >}} {{< /card-grid >}} +### In Preview + +The following integrations are in Preview. Sign up to get early access. + +{{< card-grid card_width="200px" >}} + {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" src="integrations_logos/bugsnag.png" alt="BugSnag" title="BugSnag" >}} + {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Coralogix" >}} + {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Cronitor" >}} + {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" src="integrations_logos/uptime.png" alt="uptime.com" title="uptime.com" >}} + {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Dynatrace" >}} +{{< /card-grid >}} + +{{< beta-callout url="https://www.datadoghq.com/product-preview/on-call-integrations/" >}} +These On-Call integrations are in Preview. Request access to join the waiting list. +{{< /beta-callout >}} + ## Other tools If your tool is not listed above, use the [Datadog Events API][1] to trigger On-Call pages from any source that can make an HTTP request. From 3288b43c3c67d08a7c386b41bc89fdb1cb265b25 Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Fri, 3 Jul 2026 17:27:15 +0200 Subject: [PATCH 13/15] change cards UI to match what is shown in the integation page --- .../incident_response/on-call/integrations.md | 45 ++++++++----------- layouts/shortcodes/integration-tile-grid.html | 4 ++ layouts/shortcodes/integration-tile.html | 38 ++++++++++++++++ 3 files changed, 61 insertions(+), 26 deletions(-) create mode 100644 layouts/shortcodes/integration-tile-grid.html create mode 100644 layouts/shortcodes/integration-tile.html diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 66e0eab66ca..2a02fd1105e 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -16,35 +16,28 @@ further_reading: Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party tools to send Pages directly to your On-Call teams, so alerts from any part of your stack reach the right responders through your configured escalation policies. -{{< card-grid card_width="200px" >}} - {{< image-card href="/incident_response/on-call/pages/#through-slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} - {{< image-card href="/incident_response/on-call/pages/#through-microsoft-teams" src="integrations_logos/microsoft_teams.png" alt="Microsoft Teams" title="Microsoft Teams" >}} - {{< image-card href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} - {{< image-card href="/integrations/pingdom/#page-a-datadog-on-call-team" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} - {{< image-card href="/integrations/sentry/#page-a-datadog-on-call-team" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} - {{< image-card href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} - {{< image-card href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} - {{< image-card href="/integrations/zabbix/#trigger-on-call-pages" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} - {{< image-card href="/integrations/nagios/?tab=host#trigger-on-call-pages" src="integrations_logos/nagios.png" alt="Nagios" title="Nagios" >}} - {{< image-card href="/integrations/catchpoint/#events" src="integrations_logos/catchpoint.png" alt="Catchpoint" title="Catchpoint" >}} -{{< /card-grid >}} - -### In Preview - -The following integrations are in Preview. Sign up to get early access. - -{{< card-grid card_width="200px" >}} - {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" src="integrations_logos/bugsnag.png" alt="BugSnag" title="BugSnag" >}} - {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Coralogix" >}} - {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Cronitor" >}} - {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" src="integrations_logos/uptime.png" alt="uptime.com" title="uptime.com" >}} - {{< image-card href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Dynatrace" >}} -{{< /card-grid >}} - {{< beta-callout url="https://www.datadoghq.com/product-preview/on-call-integrations/" >}} -These On-Call integrations are in Preview. Request access to join the waiting list. +To use an integration marked "Preview", or to request a new integration, request access. {{< /beta-callout >}} +{{< integration-tile-grid >}} + {{< integration-tile href="/incident_response/on-call/pages/#through-slack" logo_id="slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} + {{< integration-tile href="/incident_response/on-call/pages/#through-microsoft-teams" logo_id="microsoft-teams" src="integrations_logos/microsoft_teams.png" alt="Microsoft Teams" title="Microsoft Teams" >}} + {{< integration-tile href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" logo_id="prometheus" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} + {{< integration-tile href="/integrations/pingdom/#page-a-datadog-on-call-team" logo_id="pingdom" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} + {{< integration-tile href="/integrations/sentry/#page-a-datadog-on-call-team" logo_id="sentry" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} + {{< integration-tile href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" logo_id="amazon-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} + {{< integration-tile href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" logo_id="azure" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}} + {{< integration-tile href="/integrations/zabbix/#trigger-on-call-pages" logo_id="zabbix" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} + {{< integration-tile href="/integrations/nagios/?tab=host#trigger-on-call-pages" logo_id="nagios" src="integrations_logos/nagios.png" alt="Nagios" title="Nagios" >}} + {{< integration-tile href="/integrations/catchpoint/#events" logo_id="catchpoint" src="integrations_logos/catchpoint.png" alt="Catchpoint" title="Catchpoint" >}} + {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" logo_id="bugsnag" src="integrations_logos/bugsnag.png" alt="BugSnag" title="BugSnag" preview="true" >}} + {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Coralogix" preview="true" >}} + {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Cronitor" preview="true" >}} + {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" logo_id="uptime" src="integrations_logos/uptime.png" alt="uptime.com" title="uptime.com" preview="true" >}} + {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Dynatrace" preview="true" >}} +{{< /integration-tile-grid >}} + ## Other tools If your tool is not listed above, use the [Datadog Events API][1] to trigger On-Call pages from any source that can make an HTTP request. diff --git a/layouts/shortcodes/integration-tile-grid.html b/layouts/shortcodes/integration-tile-grid.html new file mode 100644 index 00000000000..7abac525bd1 --- /dev/null +++ b/layouts/shortcodes/integration-tile-grid.html @@ -0,0 +1,4 @@ +{{ $inner := .Inner }} +
+ {{ $inner }} +
diff --git a/layouts/shortcodes/integration-tile.html b/layouts/shortcodes/integration-tile.html new file mode 100644 index 00000000000..ef197867846 --- /dev/null +++ b/layouts/shortcodes/integration-tile.html @@ -0,0 +1,38 @@ +{{ $href := .Get "href" }} +{{ $logo_id := .Get "logo_id" }} +{{ $src := .Get "src" }} +{{ $alt := .Get "alt" | default "" }} +{{ $title := .Get "title" }} +{{ $preview := .Get "preview" }} + +{{ $int_logo := "" }} +{{ with $logo_id }} + {{ $int_logo = partialCached "integrations-logo.html" (dict "context" $ "basename" . "variant" "avatar") . "avatar" }} +{{ end }} +{{ if not $int_logo }} + {{ with $src }} + {{ $int_logo = (print $.Site.Params.img_url "images/" .) | safeURL }} + {{ end }} +{{ end }} + +
+
+ {{ if eq $preview "true" }} +
+

Preview

+
+ {{ end }} +
+ + {{ with $int_logo }} + + {{ $alt }} + +
{{ $title }}
+ {{ else }} +
{{ $title }}
+ {{ end }} + +
+
+
From 53f8aa1eaa58ac93c01351fdcf4857b52fc0955b Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Fri, 3 Jul 2026 18:08:32 +0200 Subject: [PATCH 14/15] Add Sumo Logic and New Relic integrations --- content/en/incident_response/on-call/integrations.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 2a02fd1105e..9c49bedc56b 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -31,6 +31,8 @@ To use an integration marked "Preview", or to request a new integration, request {{< integration-tile href="/integrations/zabbix/#trigger-on-call-pages" logo_id="zabbix" src="integrations_logos/zabbix.png" alt="Zabbix" title="Zabbix" >}} {{< integration-tile href="/integrations/nagios/?tab=host#trigger-on-call-pages" logo_id="nagios" src="integrations_logos/nagios.png" alt="Nagios" title="Nagios" >}} {{< integration-tile href="/integrations/catchpoint/#events" logo_id="catchpoint" src="integrations_logos/catchpoint.png" alt="Catchpoint" title="Catchpoint" >}} + {{< integration-tile href="/integrations/sumo-logic/#trigger-on-call-pages" logo_id="sumo-logic" src="integrations_logos/sumo_logic.png" alt="Sumo Logic" title="Sumo Logic" >}} + {{< integration-tile href="/integrations/new-relic/#trigger-on-call-pages" logo_id="new-relic" src="integrations_logos/new_relic.png" alt="New Relic" title="New Relic" >}} {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" logo_id="bugsnag" src="integrations_logos/bugsnag.png" alt="BugSnag" title="BugSnag" preview="true" >}} {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Coralogix" preview="true" >}} {{< integration-tile href="https://www.datadoghq.com/product-preview/on-call-integrations/" title="Cronitor" preview="true" >}} From 64adf051781f629286fd2a9c0796d8c587bec6fa Mon Sep 17 00:00:00 2001 From: "simone.tafaro" Date: Fri, 3 Jul 2026 18:24:35 +0200 Subject: [PATCH 15/15] update pingdom logo --- content/en/incident_response/on-call/integrations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/incident_response/on-call/integrations.md b/content/en/incident_response/on-call/integrations.md index 9c49bedc56b..d13cdddea43 100644 --- a/content/en/incident_response/on-call/integrations.md +++ b/content/en/incident_response/on-call/integrations.md @@ -24,7 +24,7 @@ To use an integration marked "Preview", or to request a new integration, request {{< integration-tile href="/incident_response/on-call/pages/#through-slack" logo_id="slack" src="integrations_logos/slack.png" alt="Slack" title="Slack" >}} {{< integration-tile href="/incident_response/on-call/pages/#through-microsoft-teams" logo_id="microsoft-teams" src="integrations_logos/microsoft_teams.png" alt="Microsoft Teams" title="Microsoft Teams" >}} {{< integration-tile href="/integrations/prometheus/?tab=v2preferred#prometheus-alertmanager" logo_id="prometheus" src="integrations_logos/prometheus.png" alt="Prometheus Alertmanager" title="Prometheus Alertmanager" >}} - {{< integration-tile href="/integrations/pingdom/#page-a-datadog-on-call-team" logo_id="pingdom" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} + {{< integration-tile href="/integrations/pingdom/#page-a-datadog-on-call-team" logo_id="pingdom-v3" src="integrations_logos/pingdom.png" alt="Pingdom" title="Pingdom" >}} {{< integration-tile href="/integrations/sentry/#page-a-datadog-on-call-team" logo_id="sentry" src="integrations_logos/sentry.png" alt="Sentry" title="Sentry" >}} {{< integration-tile href="/integrations/amazon-sns/#page-a-datadog-on-call-team-from-sns" logo_id="amazon-sns" src="integrations_logos/amazon_sns.png" alt="Amazon CloudWatch" title="Amazon CloudWatch" >}} {{< integration-tile href="/integrations/azure-monitor-alerts/#page-a-datadog-on-call-team" logo_id="azure" src="integrations_logos/azure.png" alt="Azure Monitor" title="Azure Monitor" >}}