Skip to main content

Overview

Rootly’s Datadog integration connects your monitoring stack to your incident response process. When a Datadog monitor fires, Rootly can receive the alert, route it to the right team, and automatically kick off an incident — all without manual intervention. During incidents, Rootly workflows can also pull Datadog notebooks, graph snapshots, and dashboards directly into the incident record.

Features

Alert Ingestion

Receive Datadog monitor alerts in Rootly via webhooks and route them to on-call or incident workflows.

On-Call Paging

Page a specific user, team, escalation policy, or service directly from a Datadog alert payload.

Notebook Automation

Create Datadog notebooks automatically from Rootly workflow actions during incidents.

Snapshot & Dashboard Retrieval

Pull Datadog graph snapshots and dashboards into incident records via workflow actions.

Before You Begin

Rootly recommends performing the installation with a service account to ensure the integration does not break if the installing user leaves the company. Ensure you are logged in as an Admin in Rootly.
You will need three pieces of information from Datadog:
  • Host — your Datadog account’s API hostname
  • API Key — authenticates Rootly with your Datadog organization
  • Application Key — grants Rootly permission to read dashboards

Plan Requirements

  • Datadog account with Admin access
  • Rootly account with Owner or Admin role

Installation

1

Open Rootly Integrations

Navigate to Configuration → Integrations in Rootly, search for Datadog, and click Setup.
Datadog integration card in Rootly's integrations catalog
2

Create an API Key in Datadog

In Datadog, navigate to Organization Settings → API Keys and click + New Key.
Creating a new API key in Datadog organization settings
Name the key (for example, Rootly Integration) and click Create Key. Copy the key immediately.
The API key value is only shown once at creation. Copy it before closing the dialog — not the Key ID.
3

Create an Application Key in Datadog

In Datadog, navigate to Personal Settings → Security → Application Keys and click + New Key.
Creating a new application key in Datadog personal settings
Name the key (for example, Rootly Integration), then edit its scope to include Read permission for Dashboards.
Adding dashboard read scope to the Datadog application key
Copy the application key.
Rootly only requires dashboard_read scope. You can add more permissions if needed for other integrations, but this is the minimum required.
4

Enter credentials in Rootly

Back in the Rootly setup form, enter:
  • Host — your Datadog API hostname. Common values:
  • API Key — paste the API key you created
  • Application Key — paste the application key you created
Click Connect.
Datadog integration configuration form in Rootly
5

Confirm connection

Datadog will appear as Connected in your integrations list.
Datadog showing as connected in Rootly's integrations list

Ingest Datadog Alerts

Once Datadog is connected, forward monitor alerts to Rootly via a webhook. Alerts received in Rootly can be routed to a Slack channel, used to page on-call responders, or trigger incident workflows automatically.

Step 1: Set Up the Webhook in Datadog

1

Install the Webhooks integration

In Datadog, navigate to Integrations, search for Webhooks, and click Install.
Installing the Webhooks integration in Datadog
2

Create a new webhook

Switch to the Configuration tab and click + New to add a webhook.
Configuration tab in Datadog Webhooks showing the New button
3

Configure the webhook

Fill in the following fields:Name — give the webhook a descriptive name (for example, Rootly_Alerts)URL — enter:
Payload — choose based on your use case:
Use this payload for standard alerts that appear in Rootly’s Alerts page without paging anyone.
The only difference between these payloads is the notification_target object. Including it tells Rootly who to page when the alert is received.
4

Add the custom header

Check the Custom Headers box and add the following, replacing the value with your Rootly webhook secret:
To find your secret:
  1. In Rootly, go to Alerts → Sources → Datadog and click Configure
Configure button on the Datadog alert source in Rootly
  1. Find the Connection Instructions panel on the right
Connection Instructions panel showing the webhook URL and secret
  1. Copy the secret value from the Custom Headers section
Custom Headers section showing the secret to copy
5

Save the webhook

Click Save.

Step 2: Attach the Webhook to a Monitor

1

Open a monitor

In Datadog, navigate to Monitors → New Monitor and choose a monitor type, or open an existing monitor to edit it.
2

Add the webhook to notifications

In the Configure notifications and automations section, reference your webhook using @webhook-<WEBHOOK_NAME> syntax (for example, @webhook-Rootly_Alerts).
3

Test and save

Click Test Notifications to confirm the alert reaches Rootly, then save the monitor.
Datadog monitor notification configuration with webhook
Successful test notification in Datadog
Verify the alert appeared on the Alerts page in Rootly.

Step 3: Build Alert Workflows in Rootly

With alerts flowing into Rootly, create a workflow that reacts to them. Alert workflows let you check alert fields, apply conditions, and trigger automated actions like creating an incident or notifying responders.
1

Open Workflows

Navigate to Workflows in Rootly and click Create Workflow.
Create Workflow button in Rootly's Workflows page
2

Choose Alert workflow type

Select Alert as the workflow type. This workflow triggers whenever Rootly receives an alert from Datadog.
Selecting Alert as the workflow type in Rootly
3

Set the trigger

Select Alert Created to fire on new alerts, or Alert Status Updated to react when an existing alert changes.
Available triggers: Alert Created fires when a new alert is received. Alert Status Updated fires when an existing alert changes state.
4

Add conditions

Filter which alerts should trigger this workflow. Common patterns:
Add a condition where Source is Datadog to scope the workflow to Datadog alerts only.
Use Datadog payload fields like alert_priority, alert_status, alert_type, and alert_title to build precise conditions.
5

Add actions

Add one or more actions to execute when the workflow fires:
You can chain multiple actions for a complete response process — for example, create an incident and then send a Slack message in the same workflow.
6

Save the workflow

Name the workflow (for example, Create Incident from Datadog P1 Alert) and click Create Workflow.
Save and create the alert workflow in Rootly

Verify the Workflow

After saving the workflow:
  1. Return to Datadog and trigger a test alert from your monitor by clicking Test Notifications
  2. Confirm the workflow activates in Rootly and performs the expected actions
  3. View the run log under Workflows → History in Rootly
You have successfully built a Datadog alert workflow in Rootly!

Workflow Actions

Create Datadog Notebook

Use this action to automatically create a Datadog notebook when an incident starts or reaches a specific status. Notebooks are useful for capturing investigation notes, timelines, and graphs in a single Datadog-native view.
1

Open workflow creation

Navigate to Workflows in Rootly and click Create Workflow, or open an existing workflow to edit it.
2

Add the action

Click Add Action, search for Datadog, and select Create Datadog Notebook.
3

Configure the action

4

Save the workflow

Click Add, name the workflow, and click Create Workflow.

Get Datadog Graph Snapshot

Use this action to capture a point-in-time graph from Datadog and attach it to the incident. This is useful for preserving the state of a metric at the time an incident was declared or escalated.
1

Add the action

In your workflow, click Add Action, search for Datadog, and select Get Datadog Graph Snapshot.
2

Configure the action

Get Datadog Dashboard

Use this action to retrieve a Datadog dashboard and surface its URL in the incident timeline. This gives responders quick access to the relevant monitoring view without leaving Rootly.
1

Add the action

In your workflow, click Add Action, search for Datadog, and select Get Datadog Dashboard.
2

Configure the action

Alert Workflow Patterns

In addition to incident workflow actions, you can build Alert workflows in Rootly that trigger automatically when a Datadog alert arrives. These are separate from incident workflows and configured under Workflows → Alert. Common patterns:
  • Auto-create an incident when a SEV-1 Datadog alert fires
  • Page on-call for alerts with alert_priority of P1 or P2
  • Send a Slack message to a channel when a monitor transitions to ALERT
  • Resolve the alert automatically when Datadog sends a RECOVERY transition
To scope workflows to Datadog only, add a condition where Source is Datadog, or filter on payload fields like alert_priority, alert_title, or alert_transition.

Uninstall

To remove the Datadog integration:
  1. Go to Configuration → Integrations and find Datadog
  2. Click the Connected button to reveal the disconnect option
  3. Click Delete
Click the Connected button to reveal the Disconnect option

Frequently Asked Questions

Verify the webhook URL is exactly https://webhooks.rootly.com/webhooks/incoming/datadog_webhooks. Confirm the Custom Headers secret value matches what is shown in Alerts → Sources → Datadog → Configure in Rootly. Check that the Datadog integration is still connected under Configuration → Integrations.
Open the resource (User, Team, Escalation Policy, or Service) in Rootly and click Edit. The resource ID appears in the URL or in the edit form. Copy it and paste it into the id field of the paging payload.
Yes. Create one webhook and attach it to as many monitors as needed by adding @webhook-<WEBHOOK_NAME> to each monitor’s notification body. Each alert will appear separately in Rootly’s Alerts page.
Alert workflows in Rootly support Alert Created (fires on new alerts) and Alert Status Updated (fires when an existing alert changes). Use conditions to filter by source (Datadog), payload fields like alert_priority or alert_title, or alert status.
By default, Rootly only pages for CRITICAL alerts from Datadog. WARNING vs. CRITICAL is the monitor’s alert_status field in the webhook payload — not alert_priority (which is your monitor’s P1–P5 importance and is independent of state). To extend paging to WARNING alerts, either configure your monitor to fire on the threshold you want treated as paging-eligible, or build an alert workflow that matches alert_status equals Warn (or Warning, depending on the value Datadog sends) and routes to the same target as CRITICAL.

Workflow Questions

Check the workflow run log in Rootly for error details. Confirm the Datadog Application Key has sufficient permissions and that the integration is still connected under Configuration → Integrations.
Yes. Datadog actions can be combined with any other Rootly workflow actions in the same workflow — for example, create a Datadog notebook and then send a Slack message with the notebook link.
Any incident Liquid variable is supported. Use the Liquid Variable Explorer to browse available variables and preview their values.