Skip to main content
Peekaping is an open-source, self-hosted monitoring system. With a Peekaping Webhook notification channel, monitor state changes sync to Flashduty On-call: a monitor going down triggers an alert in Flashduty, and the alert recovers automatically when the monitor comes back up.

In Flashduty On-call

You can get the integration push URL in either of the following ways.

Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Peekaping, then click Save
  4. Open the generated integration card and copy the Push URL

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Peekaping and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

In Peekaping

You need Peekaping 0.0.46 or later and an account that can manage notification channels and monitors. The Peekaping server must be able to reach the Flashduty push URL.
1

Create a Webhook notification channel in Peekaping

Where: Peekaping › Notification Channels › New Notification ChannelSave the notification channel.
2

Attach the channel to monitors in Peekaping

Where: Peekaping › MonitorsOpen each monitor you want alerts for, select the channel you just created under its notification channels, and save. Peekaping sends a notification when a monitor’s state changes: down (heartbeat.status 0) triggers an alert and up (1) recovers it. There is no separate recovery switch.
3

Send a test and verify with a real outage

Where: Peekaping › Notification Channels
  1. Click Test and confirm Peekaping reports success. The test request is a fixed built-in body (monitor name Test Monitor) and only proves connectivity. Flashduty opens a separate Info alert for it that never merges with a real alert and never recovers on its own, so close it manually in Flashduty afterwards
  2. Make the monitored service unavailable and confirm a Critical active alert appears in Flashduty and the checklist’s “first event received” item turns green
  3. Restore the service and confirm the alert recovers automatically

Alert key

Flashduty uses monitor.id from the request as the Alert Key. A monitor sends the same monitor.id when it goes down and when it recovers, so the recovery closes the matching alert. heartbeat.id differs on every heartbeat and is not part of the Alert Key. Changes to the monitor name, status message, or time do not change the Alert Key. A request without monitor.id is rejected. monitor.id is unique only within one Peekaping instance, so point one Flashduty integration at a single Peekaping instance.

Status and severity

Peekaping has no severity of its own, so every down event maps to Critical. The alert title is the monitor name and the description is the heartbeat message (for example TCP connection failed: ...).

Labels

The monitor config (which holds hosts and credentials) and push_token never reach labels or the description.

Troubleshooting

  • Flashduty returns an invalid-parameter error: confirm the URL is complete and includes integration_key, and that the channel’s Request Body is application/json; the response names the missing field
  • The Peekaping test fails: confirm the Peekaping server can reach the Flashduty push URL, and check the Peekaping log for the HTTP status code
  • The alert does not recover: confirm the monitor has actually returned to the up state and the notification channel is still attached to it
  • Repeated down notifications: if the monitor sets a Resend Interval, down notifications repeat while it stays down; Flashduty merges them into the same alert by Alert Key