alertmanager-main in the openshift-monitoring project). The official documentation lists PagerDuty, Webhook, Email, Slack and Microsoft Teams as receiver types, and states that the features of a supported upstream Alertmanager version are supported in OpenShift as well. The webhook receiver sends Alertmanager JSON to the URL you set (version is 4; each alert carries status, labels, annotations, startsAt, endsAt, generatorURL, fingerprint). The Flashduty Prometheus Alertmanager integration accepts this format, so no separate OpenShift integration is needed: create a Prometheus Alertmanager integration in Flashduty and configure its push URL as a webhook receiver in the OpenShift Alertmanager.
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 Red Hat OpenShift.Use a dedicated integration
- In the Flashduty console, go to Channels and open a channel
- Go to Settings → Integrations → Dedicated integrations and click Add integration
- Select Prometheus Alertmanager and click Save
- 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
- In the Flashduty console, go to Integration Center → Alert Events
- Select Prometheus Alertmanager 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 in OpenShift
The OpenShift documentation offers two ways to configure a receiver; use either one. Both require thecluster-admin role.
1
Add a webhook receiver in OpenShift
The OpenShift documentation offers two ways to configure the receiver; use either one. Both need
cluster-admin permission.- Web console
- Edit the alertmanager-main secret
Where: OpenShift console (Administrator perspective) › Administration › Cluster Settings › Configuration › Alertmanager › Create Receiver
Per the documentation, firing alerts whose labels match all selectors are sent to the receiver; add labels in Routing labels if you want label values matched exactly. Click Create when done.
2
Verify trigger and recovery
Where: A terminal that can reach the cluster (oc)Trigger a cluster alert (the OpenShift documentation points to the Red Hat Customer Portal article “Send test alerts to Alertmanager in OpenShift 4”) and confirm Flashduty receives an active alert; after it resolves, confirm the original alert closes in Flashduty.
Field mapping
One notification can carry several alerts, and Flashduty handles each one separately (up to 100 per request).
Recovery and deduplication
send_resolveddefaults totruefor the Alertmanager webhook receiver. On recovery it sends a notification withstatusset toresolved, and Flashduty closes the alert with the samefingerprint.- If you turn resolved notifications off under Show advanced configuration (or set
send_resolved: falsein YAML), Flashduty receives no recovery requests; enable auto-resolve timeout on the channel. - Alertmanager repeats notifications for alerts that are still firing, per
repeat_interval; Flashduty deduplicates byfingerprint, so no duplicate alerts are created.
Troubleshooting
- Flashduty returns
Invalid parameters: the push URL is incomplete,integration_keyis missing, or the integration type is not Prometheus Alertmanager - Alerts do not resolve: confirm the receiver does not set
send_resolved: false - No alerts arrive: confirm the route
matchersor Routing labels match the alert labels and the cluster can reachapi.flashcat.cloud(with a cluster-wide HTTP proxy, see theproxy_from_environmentnote in the OpenShift documentation);oc exec alertmanager-main-0 -n openshift-monitoring -- amtool config routes show --alertmanager.url http://localhost:9093shows the effective routes