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, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Pulseway, then 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 Pulseway 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
Configure Pulseway
Pulseway notification webhooks are created through the REST API. One webhook covers every device in the selected organizations, and nothing is installed on the devices.1
Create a REST API token in Pulseway
Where: Pulseway web app › Administration › Configuration › API Access › Third-Party Access › Create Token
After creation, note the token ID and token secret (shown only once). The REST API uses HTTP Basic authentication with the token ID as the user name and the token secret as the password. Flashduty does not need this token.
2
Create the notification webhook through the REST API
Where: Any terminal that can reach the Pulseway API › For a self-hosted Pulseway Enterprise Server, replace
POST /v3/notifications/webhookshttps://api.pulseway.com/v3/ with https://<your-server-name>/api/v3/.The Id in the response is the webhook ID; use GET, PATCH or DELETE /v3/notifications/webhooks/<Id> to view, change or delete the webhook later. The SecretKey in the response is what Pulseway uses to compute the x-hmac-signature header. Flashduty identifies the integration by the integration_key in the push URL and does not check that header, so you do not need to keep the key. Protect the push URL like a secret.3
Turn on the auto-resolve timeout in Flashduty
Where: Flashduty console › Channels › Create Channel (for an existing channel, edit it on its detail page)
A Pulseway notification is a one-shot event: when the problem clears, Pulseway sends no recovery notification. In the channel that receives these alerts, turn on the auto-resolve timeout. Closing the incident also closes its alerts.
4
Trigger a notification in Pulseway and confirm
On a monitored test device, trigger a notification at one of the selected priorities, for example by stopping a monitored service.Back in Flashduty, the integration shows Latest event time and the matching alert appears, which means the setup works.
Alert key
Flashduty uses the notificationId as the Alert Key, so each notification opens its own alert. While a problem persists, Pulseway notifies again with a new Id, which opens a new alert; the channel can group these alerts into one incident by rule. A device coming back online is a separate notification in Pulseway and does not close the earlier alert.
Status and severity
Priority matching is case-insensitive.
Labels
The alert title is the notification
Title and the description is the notification Message.
FAQ
No alert appears in Flashduty after creating the webhook?
No alert appears in Flashduty after creating the webhook?
Use
GET /v3/notifications/webhooks to confirm that Url is the full push URL and that Priorities includes the priority of the notifications that actually fire. With only Critical selected, an environment without serious problems sends nothing.Do I need to configure signature verification?
Do I need to configure signature verification?
No. Flashduty identifies the integration only by
integration_key and does not check x-hmac-signature.Why does the alert never close?
Why does the alert never close?
Pulseway sends no recovery notification. Turn on the auto-resolve timeout of the channel, or close the alert in Flashduty by hand.