Incident Ingest

Datadog + Alert24 Integration: Forward Monitor Alerts as Incidents

Send Datadog monitor alerts to Alert24 automatically using a webhook notification channel. Includes severity mapping, deduplication, and payload template.

Datadog's webhook notification channel can POST to any URL when a monitor fires. By pointing it at Alert24's incidents API, every Datadog alert automatically becomes a tracked incident — with severity mapping and deduplication.

Before you start

You'll need:

  • An Alert24 API key with write or incidents scope (Settings → API Keys)
  • Datadog account access to create webhooks and edit monitor notifications

Create the webhook in Datadog

  1. In Datadog, go to Integrations → Webhooks
  2. Click + New
  3. Set Name to alert24-incidents
  4. Set URL to https://app.alert24.net/api/v1/incidents
  5. Under Custom Headers, add:
    Authorization: Bearer ak_live_YOUR_KEY
    Content-Type: application/json
    
  6. Set the Payload to:
    {
      "title": "$EVENT_TITLE",
      "description": "$TEXT_ONLY_MSG",
      "severity": "$ALERT_PRIORITY",
      "alias": "datadog-$ALERT_ID",
      "source": "datadog",
      "tags": $TAGS_JSON
    }
    
  7. Click Save

Severity mapping

Datadog uses P1–P5 priorities. Alert24 accepts critical, high, medium, low, and info. Map them in the payload using Datadog template variables — or simplify by sending a fixed severity and adjusting per monitor.

Datadog Alert24
P1 critical
P2 high
P3 medium
P4 low
P5 info

To map automatically, you can use a Datadog webhook template variable transformer — or create separate webhooks per priority tier.

Add the webhook to a monitor

In any Datadog monitor's Notify your team section, add:

@webhook-alert24-incidents

To notify only on alert (not recovery), use:

{{#is_alert}}@webhook-alert24-incidents{{/is_alert}}

Deduplication

The alias field uses $ALERT_ID — Datadog's stable monitor event identifier. If the same monitor fires multiple times, Alert24 increments the occurrence count on the existing open incident rather than creating duplicates.

Tips

  • Recovery: To auto-resolve the Alert24 incident when a monitor recovers, you'd need a second webhook that calls PUT /api/v1/incidents with status: resolved using the same alias to look up the incident. Alternatively, let Alert24's own monitoring detect the recovery independently.
  • $TAGS_JSON: Datadog provides this as a JSON array, so it maps directly to Alert24's tags array field.
  • Selective forwarding: Rather than adding the webhook to every monitor, add it only to production-critical monitors to avoid alert fatigue.