Monitoring and observability for infrastructure, applications and logs.
Get notified on your phone the moment a Datadog webhook fires. No more checking dashboards.
Choose exactly which Datadog events trigger notifications. Filter out the noise.
Control who on your team gets notified and how: push notifications, record only, or both.
Copy a webhook URL, paste it in Datadog, and you're done. No code required.
| Event | Sample notification |
|---|---|
|
Monitor still warning
Re-Warn
⚠️ [Re-Warn on {host:ip-012345}] Memory usage is high
Memory usage on ip-012345 is above 85%.
|
⚠️ [Re-Warn on {host:ip-012345}] Memory usage is high
Memory usage on ip-012345 is above 85%.
|
|
Monitor triggered
Triggered
🚨 [Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
🚨 [Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
|
Monitor still has no data
Re-No Data
❔ [Re-No Data on {host:ip-012345}] Memory usage is high
The monitor is still not receiving data - host:ip-012345
|
❔ [Re-No Data on {host:ip-012345}] Memory usage is high
The monitor is still not receiving data - host:ip-012345
|
|
Monitor still alerting
Re-Triggered
🚨 [Re-Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
🚨 [Re-Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
|
Monitor recovered
Recovered
✅ [Recovered on {host:ip-012345}] Host is Down
The host ip-012345 is reporting again.
|
✅ [Recovered on {host:ip-012345}] Host is Down
The host ip-012345 is reporting again.
|
|
Monitor warning
Warn
⚠️ [Warn on {host:ip-012345}] Memory usage is high
Memory usage on ip-012345 is above 85%.
|
⚠️ [Warn on {host:ip-012345}] Memory usage is high
Memory usage on ip-012345 is above 85%.
|
|
Monitor reminder
Renotify
🔔 Reminder: [Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
🔔 Reminder: [Triggered on {host:ip-012345}] Host is Down
The host ip-012345 stopped reporting to Datadog.
|
|
Monitor has no data
No Data
❔ [No Data on {host:ip-012345}] Memory usage is high
The monitor stopped receiving data - host:ip-012345
|
❔ [No Data on {host:ip-012345}] Memory usage is high
The monitor stopped receiving data - host:ip-012345
|
hookfire and paste your Hookfire webhook URL. {
"transition": "$ALERT_TRANSITION",
"alert_type": "$ALERT_TYPE",
"alert_title": "$ALERT_TITLE",
"event_title": "$EVENT_TITLE",
"body": "$TEXT_ONLY_MSG",
"link": "$LINK",
"monitor_id": "$ALERT_ID",
"hostname": "$HOSTNAME",
"priority": "$ALERT_PRIORITY",
"scope": "$ALERT_SCOPE",
"date": "$DATE_POSIX",
"org": "$ORG_NAME"
}
@webhook-hookfire to the notification message. Datadog does not sign webhooks, so Hookfire checks a secret header instead:
HOOKFIRE_SECRET with that string as the value and tick hide from view. {"X-Hookfire-Secret": "$HOOKFIRE_SECRET"}. On your Hookfire integration page, toggle on the transitions you want to receive push notifications for. Most people take Triggered and Recovered, and mark Triggered high priority.
Click the Test button next to an event on your integration page, or use Test Notifications on a monitor that mentions @webhook-hookfire.
| Event | Description |
|---|---|
Triggered |
A monitor went into alert |
Re-Triggered |
A monitor is still alerting after renotifying |
Warn |
A monitor passed its warning threshold |
Re-Warn |
A monitor is still warning after renotifying |
No Data |
A monitor stopped receiving data |
Re-No Data |
A monitor still has no data after renotifying |
Recovered |
A monitor recovered |
Renotify |
A reminder for a monitor that is still alerting |
The event is Datadog’s $ALERT_TRANSITION, which is why the payload above sends it as transition.
Reference: Datadog Webhooks integration.
Start receiving instant push notifications for your Datadog webhooks. Free to start, no credit card required.
Get Started Free