Skip to main content
CubeAPM can send alert notifications by HTTP POST to any webhook URL. The default JSON body is compatible with the Prometheus Alertmanager webhook format (receiver, status, alerts, groupLabels, commonLabels, commonAnnotations, externalURL, and so on; each alert carries status, labels, annotations, startsAt, endsAt, generatorURL, fingerprint, plus CubeAPM’s own cubeImageURL and cubeSampleLog). The Flashduty Prometheus Alertmanager integration accepts this format, so no separate CubeAPM integration is needed: create a Prometheus Alertmanager integration in Flashduty and paste its push URL into CubeAPM.

In Flashduty On-call

Get an integration push URL in either of the two ways below. Choose the Prometheus Alertmanager integration type in both, not CubeAPM.

Use a dedicated integration

  1. In the Flashduty console, go to Channels and open a channel
  2. Go to Settings → Integrations → Dedicated integrations and click Add integration
  3. Select Prometheus Alertmanager and click Save
  4. Open the generated integration card and copy the Push URL, in the form https://api.flashcat.cloud/event/push/alert/prometheus?integration_key=<integration key>

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Prometheus Alertmanager 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 in CubeAPM

1

Create a webhook receiver in CubeAPM

Configure the receiver when you create an alert in CubeAPM (the official documentation gives no menu path for this entry, so none is written here):The CubeAPM documentation states that the webhook JSON body is Alertmanager-compatible by default and can be customized with a Go template in Payload. If you customize it, keep the Alertmanager-style alerts array and make every alert carry status, labels, annotations, startsAt, endsAt and fingerprint; otherwise Flashduty cannot tell trigger from recovery or match a recovery to its alert.
2

Trigger an alert and verify

Let a CubeAPM alert rule fire and confirm Flashduty receives an active alert; after it resolves, confirm the original alert closes in Flashduty. The CubeAPM documentation does not say whether the webhook has a test-send function, so verify with a real alert.After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Field mapping

One notification can carry several alerts, and Flashduty handles each one separately (up to 100 per request).

Recovery and deduplication

  • When CubeAPM sends a notification whose status is not firing (for example resolved), Flashduty closes the alert with the same fingerprint. CubeAPM’s own PagerDuty and Zenduty examples likewise map any non-firing status to a resolve.
  • The CubeAPM documentation does not say whether the webhook has a test-send function. After the first setup, verify with a real alert that both trigger and recovery appear in Flashduty.

Troubleshooting

  • Flashduty returns Invalid parameters: the push URL is incomplete, integration_key is missing, or the integration type is not Prometheus Alertmanager
  • Alerts do not resolve: confirm that every alert in a customized Payload has status and fingerprint, and that the recovery notification carries the same fingerprint as the trigger
  • No alerts arrive: confirm CubeAPM can reach api.flashcat.cloud and that the alert rule uses this webhook receiver