Send Alertmanager alerts to Acked

Native Alertmanager v4 parsing: batches fan out, repeats deduplicate, resolved alerts close.

Acked reads each item in Alertmanager's alerts array. Each firing alert becomes its own Acked alert. Its string labels can route it to an Acked service.

1. Create the Acked connection

Open Integrations → Sources → Add vendor connection and choose Prometheus Alertmanager. Select a fallback service. Add ordered routing rules over Alertmanager labels when the connection serves several services. Save it and copy the ingest URL. Treat that URL as a credential.

2. Configure a receiver

Add an Acked receiver in alertmanager.yml:

receivers:
  - name: acked
    webhook_configs:
      - url: https://api.acked.dev/v1/ingest/ik_<id>_<secret>
        send_resolved: true

Route the desired alerts to that receiver, then reload Alertmanager using your normal deployment process.

What Acked maps

• fingerprint → stable event key for deduplication and resolve.
• annotations.summary, then labels.alertname → title.
• annotations.description → body.
• labels.severity → Acked priority.
• Each string label → an available routing attribute.
• Per-alert status: resolved → resolve action.

Acked evaluates routing for each item. Alerts in one batch can reach different services. The fallback service receives unmatched alerts. If an alert has no fingerprint, Acked derives a deterministic key from its labels. Unknown severity values stay paging-high rather than being silently downgraded.

3. Test a firing and resolution

Send a real test rule through the route. Confirm one page arrives, repeat notification deduplicates, and send_resolved closes the alert.