Skip to main content
The Datadog monitor connector uses a managed webhook payload so firing, renotify, and recovery notifications keep one stable Squasher incident.

​
Connect Datadog

1

Create the Squasher source

Create a Datadog monitors source under Settings → Integrations. Copy its endpoint and generated secret.
2

Add a Datadog webhook

In Datadog, open Integrations → Webhooks, create a webhook, and set its URL to the Squasher endpoint.
3

Add the authentication header

Set Custom Headers to the JSON below.
4

Use the Squasher payload template

Paste this JSON into Payload.
5

Notify the webhook

Add @webhook-<WEBHOOK_NAME> to each Datadog monitor that should create a Squasher incident. Trigger and recover a test alert.

​
Incident behavior

  • $ALERT_CYCLE_KEY is the preferred stable key across trigger and recovery. The monitor alert ID is used only when a cycle key is unavailable.
  • Triggered, Re-Triggered, Warn, Re-Warn, No Data, Re-No Data, and Renotify are firing updates. Recovered or Resolved resolves the incident.
  • Monitor priority maps deterministically: P1/P2 → sev-1, P3 → sev-2, and P4/P5 → sev-3. An absent or unrecognized priority uses the connector’s configured default severity.
  • Tags, status message, and the Datadog link remain available for triage.
  • Retries of the same $ID are idempotent.
The adapter requires title, a transition (alert_transition or transition), and one stable identity (alert_cycle_key or alert_id). It also accepts event_id, date, message, link, tags, priority, and an optional explicit severity. If you customize the managed template with severity, project-defined severity keys or common severity names take precedence over priority. Unknown fields are ignored.
Datadog retries webhook delivery for internal errors and 5xx responses. It does not retry a request rejected for an invalid credential or payload.
If recovery creates a separate incident, confirm that $ALERT_CYCLE_KEY appears in the exact payload template. If a logs monitor omits status text, add $ALERT_STATUS to its webhook configuration. Related: Inbound alert connectors, Alert Connectors API.