monitor_offline), recovery (monitor_online) and SSL certificate expiring (certificate_expires_soon) notifications to Flashduty On-call. Each monitor maps to one Flashduty alert: the alert triggers when the monitor goes down 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 Pulsetic 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 Pulsetic 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 Pulsetic
1
Add a webhook notification in Pulsetic
Where: Pulsetic › Monitors › ··· next to the monitor › Alerts › Developer Tools › Webhook
Then click Save. You can add up to 10 different webhook URLs.You can also configure it once at the account level under Alerts so it applies to all monitors (General Alerts).
2
Send a test request (optional)
Where: Pulsetic › Monitors › ··· next to the monitor › Alerts › Developer Tools › Webhook › Send testAfter saving, click Send test to show three buttons: Send Online Request, Send Offline Request and Send SSL Expires Soon Request. The test only proves that Pulsetic can reach the push URL.
- Online, Offline or SSL: Flashduty receives an Info alert titled
Pulsetic test notificationand the monitor’s real alert is not affected. The test alert does not recover on its own, so close it manually after verifying
3
Verify the lifecycle
Where: Pulsetic › MonitorsLet a monitor go down for real (for example, point it to a URL that returns 5xx) and confirm Flashduty receives a Critical alert. Restore the target and confirm the alert closes.
Payload
Pulsetic POSTs the following fields as JSON. Flashduty parses them directly, with no template to configure:
The alert title is the monitor name. When the name is empty, the monitored URL is used.
Alert key
Flashduty usesmonitor.id as the Alert Key for down and recovery alerts. The down, repeated down and recovery notifications of one monitor carry the same monitor.id, so they land on the same alert. Renaming the monitor or changing its URL or tags does not change the Alert Key.
SSL certificate expiry notifications get their own Alert Key built from alert_type and monitor.id. Repeated reminders for one monitor merge into one alert, and they never close or update the down alert.
When monitor.id is missing, Flashduty returns a parameter error because the recovery cannot be matched to the original alert.
Status and severity
Pulsetic notifications carry no severity. Flashduty maps them as follows:
Any other
alert_type (for example, a type Pulsetic adds later) is acknowledged and ignored without creating an alert.
FAQ
Does the SSL expiry alert close on its own?
Does the SSL expiry alert close on its own?
Pulsetic sends no recovery notification for certificate reminders. Turn on auto-close in the Flashduty integration or channel, with a suggested duration of 24 hours. A new reminder after the certificate is renewed triggers again.
I did not receive an alert right after the monitor went down?
I did not receive an alert right after the monitor went down?
Pulsetic probes at the check interval set on the monitor, and you can set how long it waits after a failure before notifying under Intervals. Flashduty receives nothing until Pulsetic sends the notification.
Troubleshooting
- Pulsetic does not push: confirm the monitor’s Alerts → Webhook is saved and the Webhook URL is the complete push URL including
integration_key - Flashduty returns a parameter error: confirm the request body contains
alert_typeandmonitor.id - An alert does not recover: confirm the recovery comes from the same monitor;
monitor.idmust match