Alertmanager — `alertmanager`

A push receiver for Alertmanager : point a webhook_configs.url at this source’s ingest endpoint and every alert Alertmanager routes becomes an event. Alertmanager has already evaluated, grouped, deduped and (with send_resolved) tracks firing→resolved — NavFlow just records what it pushes, and correlates it with your other sources.

Use this over prometheus_alerts when you want Alertmanager’s grouping / silencing / resolved semantics and real-time delivery.

Set up

Agent

Ask a connected agent:

Use navflow to create an Alertmanager source and give me the webhook URL.

The agent calls create_source and returns the ingest URL to configure as an Alertmanager receiver.

Console

Sources → Add source → Alertmanager alerts. Name it and Create — the source page shows a copy-paste alertmanager.yml receiver block with the ingest URL already filled in (and the auth block when the instance requires a token).

Alertmanager config

Add the receiver to your alertmanager.yml and reload Alertmanager:


receivers:
  - name: navflow
    webhook_configs:
      - url: http://localhost:8787/ingest/<ingest_key>
        send_resolved: true
route:
  receiver: navflow

On a secured instance (navflow up --auth), add an ingest-scoped API key to the webhook_configs entry:


        http_config:
          authorization:
            type: Bearer
            credentials: <ingest-api-key>

Alertmanager POSTs a batch ({ alerts: [...], ... }); NavFlow fans out the alerts array into one event each: event_type = the alert name, text = its summary, its labels as NavFlow labels plus a synthetic status (firing / resolved). The full alert (including fingerprint) is kept in the payload.

Configuration

A push connector — no polling config. The entity key is auto-derived from a label (namespace → service → job → instance, or a declared primary label).

field	type	description
`key_label`	string · advanced	alert label to key on (default: `namespace` / `service` if present)

Verify

Send a test batch to the ingest endpoint, then check Recent events:


curl -X POST http://localhost:8787/ingest/<ingest_key> \
  -H 'Content-Type: application/json' \
  -d '{"alerts":[{"status":"firing","labels":{"alertname":"PostgresDown","severity":"critical","namespace":"prod"},"annotations":{"summary":"Postgres is down"},"startsAt":"2024-01-01T00:00:00Z"}]}'

Fields shows the alert labels, so you can promote namespace / service to correlate on.

Alertmanager — alertmanager