$EVENT_* variables. This integration therefore asks you to create the webhook integrations from the template below, and Flashduty parses exactly the output of that template. The Flashduty alert triggers when the monitor enters the alert or warning state and closes automatically when it recovers.
In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
- In the Flashduty console, go to Channels and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Edge Delta and click Save
- Open the generated integration card and copy the Push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Edge Delta and enter an integration name
- Configure the default route and select a channel. You can add more rules under Routing after creation
- Click Save and copy the generated Push URL
In Edge Delta
1
Create one webhook integration per state
Where: Edge Delta › Admin › Legacy Integrations › Available › search for and select Webhook
Create
flashduty-recovery the same way (with status set to recovery). For warnings, also create flashduty-warning (with status set to warning).The template leaves out
$EVENT_MSG, $EVENT_QUERY and $EVENT_TITLE: they can contain quotes or line breaks that make the JSON invalid, so the alert or its recovery would be lost. $EVENT_METRIC and $EVENT_EVALUATED_VALUE are empty for log monitors (log threshold, pattern anomaly); Flashduty accepts empty values.2
Reference the integrations in the monitor notification
Where: Edge Delta › edit the monitor › NotificationsReference each integration by state in Notifications (type Save the monitor.
@ to pick from the list; an integration appears as @webhook-<integration name>):{{#is_recovery}} applies when an alert or warning returns to normal.3
Verify the lifecycle
Where: Edge Delta › edit the monitor › Notifications › Test NotificationsClick Test Notifications to send a test request. Flashduty receives a Critical alert (the test request looks the same as a real alert and cannot be told apart; unless you pick a group in the test dialog, its
group is empty, so it never merges with a real alert), so close it manually after verifying. You can also let the monitor enter the alert state for real, confirm Flashduty receives the alert, and confirm it closes automatically after recovery. A few seconds later the integration in Flashduty shows a Latest event time, which means setup works.Payload
Alert key
Flashduty builds the Alert Key frommonitor and group. The alert, warning and recovery requests of one monitor (and one group) carry the same monitor and group, so they land on the same alert; different groups stay separate. A monitor without group by sends * as group, so the whole monitor maps to one alert; a monitor with group by sends <tag>:<value> (for example ed.tag:docker-logs). value, metric and the time are not part of the Alert Key.
The Edge Delta documentation does not provide a stable ID for monitor events, so the Alert Key is built from the
monitor text you type and $EVENT_GROUP_ALL. Edge Delta’s own PagerDuty example also pairs trigger and resolve on the group value.Status and severity
If
monitor or status is missing, or status is not one of the values above, Flashduty returns a parameter error.
FAQ
Why must monitor be typed instead of using a variable?
Why must monitor be typed instead of using a variable?
Among the
$EVENT_* variables listed in the Edge Delta documentation there is no monitor ID or name, only $EVENT_ID (the event ID, and the documentation does not say whether the alert and the recovery of one monitor share it). Fixed text guarantees that the alert and the recovery match.Do I get repeated notifications while the monitor stays in alert?
Do I get repeated notifications while the monitor stays in alert?
If the monitor has a renotification period, Edge Delta sends the alert request again at that interval. These requests have the same Alert Key, so Flashduty merges them into one alert and does not create a new incident.
Troubleshooting
- The monitor shows
Receiver webhook-flashduty-warning does not exist: every@webhook-...handle in the notification must match an existing integration; create it or remove its block - Edge Delta does not push: confirm the monitor’s Notifications reference
@webhook-<integration name>inside the matching{{#is_alert}}or similar block - Flashduty returns a parameter error: confirm
statusin the template isalert,warningorrecovery,monitoris not empty, and the body is valid JSON - The alert does not recover: confirm
monitorin the recovery integration is identical to the alert integration; for a monitor with group by, confirmgroupin the recovery request matches the alert