Skip to main content
The Prometheus Alertmanager connector accepts the standard webhook v4 payload. It splits a batch into individual alert lifecycles and uses each alert’s fingerprint as its stable correlation key.

​
Create the connector

Create a Prometheus Alertmanager source under Settings → Integrations. Save the returned endpoint and secret; the secret is shown only at creation or rotation.

​
Configure Alertmanager

Add a receiver and route to alertmanager.yml. Keep send_resolved: true so Squasher can resolve incidents.
Validate and reload the configuration:
Place the receiver on a narrower route instead when only selected alerts should reach Squasher.

​
Incident behavior

  • Every item in alerts is handled independently, even when the webhook groups several alerts.
  • fingerprint is the stable alert key. Repeated firing notifications update the existing incident.
  • An alert-level resolved status resolves the matching incident.
  • labels.alertname supplies the title when available. Labels, annotations, generator links, start time, and end time remain available for triage.
  • truncatedAlerts indicates that Alertmanager omitted alerts from the batch. Set max_alerts: 0 unless you intentionally limit webhook batches.

​
Test and troubleshoot

Send a temporary Prometheus alert through the route and let it recover. Confirm that one incident opens and the same incident resolves. If firing arrives but recovery does not, check send_resolved. A 401 response means the bearer credential does not match; rotate it and update alertmanager.yml together. Related: Inbound alert connectors, Alert Connectors API.