Datadog
Alerts

12min
Overview
Datadog can be configured to send events into Rootly as alerts. The alerts received on Rootly can then be routed to a Slack channel or used to initiate incidents.
Configure Webhook in Datadog
Please note that you will need to first have Datadog installed in Rootly before being able to ingest alerts from Datadog. If you have not installed Datadog in Rootly, please follow the instructions on the Installation page.
Log into your Datadog account and select: Integrations > Search for "Webhook" > Select Webhooks
﻿
You'll be asked to configure a webhook. Now, select + New in Webhooks section (lower left corner of the modal.
﻿
Once we have located the Webhook within Datadog, we would need to configure the Webhook to point to the following URL:
URL
https://webhooks.rootly.com/webhooks/incoming/datadog_webhooks
https://webhooks.rootly.com/webhooks/incoming/datadog_webhooks
﻿
﻿
You'll be promoted to enter the following details for the webhook.
﻿
Name
Give your webhook a representative name.
URL
The webhook URL can be obtained from your Datadog integration page in Rootly (Integrations > Datadog > Configure).
﻿
Payload
General Alert
Copy the following code and paste it into the Payload field. This will result in a regular (non-paging) alert.
JSON
{
"id":"$ID",
"body":"$EVENT_MSG",
"last_updated":"$LAST_UPDATED",
"event_type":"$EVENT_TYPE",
"title":"$EVENT_TITLE",
"alert_id":"$ALERT_ID",
"alert_metric":"$ALERT_METRIC",
"alert_priority":"$ALERT_PRIORITY",
"alert_query":"$ALERT_QUERY",
"alert_scope":"$ALERT_SCOPE",
"alert_status":"$ALERT_STATUS",
"alert_title":"$ALERT_TITLE",
"alert_transition":"$ALERT_TRANSITION",
"alert_type":"$ALERT_TYPE",
"date":"$DATE",
"org":{"id":"$ORG_ID","name":"$ORG_NAME"}
}
{
"id":"$ID",
"body":"$EVENT_MSG",
"last_updated":"$LAST_UPDATED",
"event_type":"$EVENT_TYPE",
"title":"$EVENT_TITLE",
"alert_id":"$ALERT_ID",
"alert_metric":"$ALERT_METRIC",
"alert_priority":"$ALERT_PRIORITY",
"alert_query":"$ALERT_QUERY",
"alert_scope":"$ALERT_SCOPE",
"alert_status":"$ALERT_STATUS",
"alert_title":"$ALERT_TITLE",
"alert_transition":"$ALERT_TRANSITION",
"alert_type":"$ALERT_TYPE",
"date":"$DATE",
"org":{"id":"$ORG_ID","name":"$ORG_NAME"}
}
﻿
Paging Rootly On-Call
Paging through Rootly On-Call also relies on webhook alerts. The main difference being the inclusion of a notification_target object.
JSON
"rootly": {
        "notification_target": {
            "type": "Service",
            "id": "00acba53-b07e-455d-add6-73263209a610"
        }
    }
"rootly": {
        "notification_target": {
            "type": "Service",
            "id": "00acba53-b07e-455d-add6-73263209a610"
        }
    }
﻿
type - this defines the Rootly resource type that will be used for paging. 
The following are the available values:User | Group (Team) | EscalationPolicy | Service
﻿
id - this specifies the exact resource that will be targeted for the page.
The id of the resource can be found when editing each resource.
﻿
Copy the following code and paste it into the Payload field. This will result in both the alert appearing in Rootly and the targeted resource being paged.
JSON
{
    "id":"$ID",
    "body":"$EVENT_MSG",
    "last_updated":"$LAST_UPDATED",
    "event_type": "composite_monitor",
    "title":"Datadog webhook alert",
    "alert_id":"$ALERT_ID",
    "alert_metric":"$ALERT_METRIC",
    "alert_priority":"$ALERT_PRIORITY",
    "alert_query":"$ALERT_QUERY",
    "alert_scope":"$ALERT_SCOPE",
    "alert_status":"$ALERT_STATUS",
    "alert_title":"$ALERT_TITLE",
    "alert_transition":"$ALERT_TRANSITION",
    "alert_type":"$ALERT_TYPE",
    "date":"$DATE",
    "org":{"id":"$ORG_ID","name":"$ORG_NAME"},
    "rootly": {
        "notification_target": {
            "type": "Service",
            "id": "00acba53-b07e-455d-add6-73263209a610"
        }
    }
}
{
    "id":"$ID",
    "body":"$EVENT_MSG",
    "last_updated":"$LAST_UPDATED",
    "event_type": "composite_monitor",
    "title":"Datadog webhook alert",
    "alert_id":"$ALERT_ID",
    "alert_metric":"$ALERT_METRIC",
    "alert_priority":"$ALERT_PRIORITY",
    "alert_query":"$ALERT_QUERY",
    "alert_scope":"$ALERT_SCOPE",
    "alert_status":"$ALERT_STATUS",
    "alert_title":"$ALERT_TITLE",
    "alert_transition":"$ALERT_TRANSITION",
    "alert_type":"$ALERT_TYPE",
    "date":"$DATE",
    "org":{"id":"$ORG_ID","name":"$ORG_NAME"},
    "rootly": {
        "notification_target": {
            "type": "Service",
            "id": "00acba53-b07e-455d-add6-73263209a610"
        }
    }
}
﻿
Custom Header
Check the Custom Header checkbox and paste the following code into the text area. 
JSON
{"secret":"a04d2feb4286150731a718acba564198605675ec191ef9ae7956c6e15af54edf"}
{"secret":"a04d2feb4286150731a718acba564198605675ec191ef9ae7956c6e15af54edf"}
﻿
Replace the secret value with the one found in your Datadog integration in Rootly (Integrations > Datadog > Configure).
﻿
Once completed, go ahead and select Save to create your webhook.
Attach Webhook to Monitor
Once your webhook is created, you need to attach it to a Datadog monitor. A monitor contains the firing logic that determines when alerts will be sent out.
Navigate to Monitor > New Monitor > Event to create a new monitor.
﻿
Now, you can configure your monitor to your desired firing logic. The main action to ensure that you do is select your webhook in the Notify your team section.
﻿
Once ready, you can select Test Notifications to test out your monitor and webhook. You should see a test alert appear from Datadog on your Rootly Alerts page.
﻿
Finally, save your monitor. The resulting product should look something like this:
﻿
Support
If you need help or more information about this integration, please contact [email protected] or start a chat by navigating to Help > Chat with Us.
Updated 17 Jan 2025
Did this page help you?
Workflows
Kubernetes