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, bound to the service where you created the source.

1. Create the Acked source

Under Services → your service → Sources → Add, choose Prometheus Alertmanager. Save it and copy the generated 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.
• Per-alert status: resolved → resolve action.

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.