Native to AlertManager

Bearer-token auth, no bespoke adapter

Drop Veirox into your existing webhook_configs block. Standard http_config.authorization.

Correlation-aware

Grouped alerts, one triage run

Veirox honours your AlertManager routing. Ten related alerts = one agent session — not ten. Saves tokens, saves noise.

Read-only first

Safe by default

Ship with the read-only triage template: kubectl get/describe, runbooks, findings. Never modifies cluster state unless you approve it.

Setup · 3 steps

From "configured" to "firing alerts" in under a minute.

1

Create the webhook in Veirox

Open /console/webhooks → click Configure Webhook → pick Prometheus AlertManager. Either reuse a triage task or pick the "AlertManager triage (read-only)" starter template from the wizard.

2

Add the receiver to `alertmanager.yml`

Copy the snippet below and paste it under receivers:. Substitute the webhook URL and token Veirox shows on create.

route:
  receiver: veirox
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 1h

receivers:
  - name: veirox
    webhook_configs:
      - url: https://ops.example.com/api/webhooks/<task_id>
        send_resolved: true
        http_config:
          authorization:
            type: Bearer
            credentials: <webhook-token>

Reload AlertManager (kill -HUP or the UI reload endpoint) after editing.

3

Fire a test alert

Use amtool or the AlertManager HTTP API:

amtool alert add \
  --alertmanager.url=http://localhost:9093 \
  alertname=VeiroxPing severity=warning

Watch the Waiting for first event card in the console flip to green.

Already running AlertManager?

You have everything you need. Open the console and connect in a minute.

Configure in the console

Also available: Grafana · PagerDuty · all 9 providers

AI triage for every AlertManager alert. Wired up in 60 seconds.