Datadog integration

Turn Datadog monitor alerts into phone calls, Telegram and escalation

Add WardenPoint as a Datadog webhook. Monitor priority (P1–P5) maps to alert severity, a recovery posts a Resolved notice, and unacknowledged alerts escalate across voice, Telegram, SMS and email.

Start free View API examples
Setup
Webhook
Severity
P1–P5
Recovery
Resolved ping

Anatomy of a Datadog alert

LIVE
Datadog → webhook
checkout p99 above SLO for 5m
WardenPoint
map priority · escalate · resolved notice
Telegram
Voice call
Email

Setup

Three steps in Datadog

Create the webhook once, then reference it from any monitor's notification message.

  1. 1Step 1

    Create a webhook

    Integrations → Webhooks → New. Name it WardenPoint.

    $ Integrations › Webhooks › New
  2. 2Step 2

    Set URL, header and payload

    Put your WardenPoint URL in the URL field, add a custom header Authorization: Bearer <your secret>, and paste the payload template below into the Payload field.

    $ URL › https://wardenpoint.com/api/v1/integrations/alerts/…
  3. 3Step 3

    Reference it from monitors

    In any monitor's notification message add {'@'}webhook-WardenPoint. Datadog fires the webhook on trigger and on recovery automatically.

    $ Monitor › Notify › {'@'}webhook-WardenPoint

Wire format

Datadog webhook payload template

Datadog builds the body from $-variables. WardenPoint maps the monitor priority to severity and the alert transition to firing or resolved.

Datadog → WardenPoint
datadog-webhook.jsonJSON
// Datadog webhook payload template ($-variables)
{
"aggreg_key": "$AGGREG_KEY",
"title": "$EVENT_TITLE",
"body": "$EVENT_MSG",
"alert_type": "$ALERT_TYPE",
"alert_transition": "$ALERT_TRANSITION",
"priority": "$PRIORITY",
"hostname": "$HOSTNAME",
"link": "$LINK",
"tags": "$TAGS"
}
WardenPoint fan-out
WardenPoint response202
{
"status": "queued",
"notification_uuid": "notif_8h2k7yQrxJp",
"channels_planned": [
"telegram_voice",
"voice_call",
"email"
],
"escalation_chain_id": "esc_4j2k9bMcvL"
}

Routing recipes

Three patterns for Datadog → WardenPoint

Run different monitor priorities or teams through separate WardenPoint integrations, each wired to its own escalation chain.

Priority

P1 → phone first

Datadog monitor priority P1 maps to WardenPoint 'critical' — phone call first, Telegram voice second, email at minute three. P4–P5 monitors stay on email.

match
$PRIORITY = P1
→ route
priority: critical
Team

Route a team's monitors to its on-call

Create a dedicated WardenPoint integration whose recipient group is the team's chain, then reference it as {'@'}webhook-<team> in just that team's monitors.

match
{'@'}webhook-payments
→ route
→ payments chain
Recovery

Recovery posts a Resolved notice

A Recovered transition POSTs to the same WardenPoint URL. WardenPoint marks the alert resolved and posts a Resolved notice to your chain.

match
$ALERT_TRANSITION = Recovered
→ route
→ Resolved notice

Datadog FAQ

Common Datadog integration questions

WardenPoint reads the monitor $PRIORITY (P1 highest … P5 lowest) and maps it to its alert priorities automatically. When a monitor has no priority set, the event $ALERT_TYPE (error / warning / info) is used instead. No hand-mapping in the template.
Free plan

Wire one Datadog monitor before you depend on it

Create the webhook, trigger a test monitor and read the audit line. No credit card. No production risk.

Start free Back to integrations
  • Priority maps to severity
  • Recovery posts a Resolved notice
  • Per-team routing