Skip to main content
Use a Bleemeo webhook integration to send metric status changes to Flashduty On-call. A metric entering Warning, Critical, or Unknown status triggers an alert, and the metric returning to OK closes the same alert.

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, go to Channels and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Bleemeo and 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 Bleemeo 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

Configure Bleemeo

1

Add a webhook notification target in Bleemeo

Where: Bleemeo › Alerting › Notification TargetsClick Save. The test carries no metric and only proves the URL is reachable; it opens a separate Info alert in Flashduty, so close it manually.
2

Select the target in a Bleemeo notification rule

Keep the scope and problem, choose Notification Targets as the target type, and select the new target. Bleemeo then sends a notification to the URL when a metric changes status, and again when it recovers.
3

Verify alert and recovery

Push a metric past its threshold (for example, temporarily lower a CPU usage threshold). After a few seconds, go back to Flashduty. If the integration shows a Latest event time and an active alert, the setup works. Restore the threshold and confirm the same alert recovers.

Payload

Bleemeo POSTs a JSON notification. Flashduty parses it directly, with no template to configure:

Alert key

Flashduty uses metric as the Alert Key. The alert and recovery notifications of one metric carry the same metric, so they land on the same alert, while different metrics produce different alerts. The top-level id is not part of the Alert Key, and changes to the title, value, or time do not change it. If metric is missing, Flashduty returns a parameter error, because a recovery cannot be reliably matched to its alert.

Status and severity

A request with an empty or any other status is rejected, so a request whose state is unclear never enters the wrong alert lifecycle.

FAQ

Refer to Bleemeo’s current plan description. Webhooks may require a higher tier, and the trial period usually includes them.
No. Bleemeo may retry failed deliveries, and notifications for one metric carry the same metric, so they merge into one alert.
No. 3 (Unknown) is handled as Warning, and only 0 (OK) closes the alert.

Troubleshooting

  • The test notification opens an Info alert: the test sent after saving a target has no metric and is recognised by its fixed body (status 10, title Test); it opens its own Info alert that never recovers, so close it manually
  • Bleemeo reports a failed delivery: confirm the webhook URL is the full push URL and includes integration_key
  • Flashduty returns a parameter error: confirm the request is a Bleemeo JSON notification with a non-empty metric and a status from 0 to 3
  • The alert does not recover: confirm the recovery is sent through the same webhook integration; the recovery and the alert must carry the same metric
For field details, see the Bleemeo documentation: Webhook.