Metrics & monitoring

Send VictoriaMetrics (vmalert) alerts to on-call with CallHeim.

vmalert alerts delivered through an Alertmanager webhook receiver pointed at CallHeim. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

victoriametricssource names also accepted: vmalert, victoria-metrics, vm

Grouped alerts

A group is split into one alert per member. An incident that holds several alerts stays open while any of them is still firing.

Setting it up

Create an Integration in CallHeim and choose VictoriaMetrics (vmalert) from the Catalog to get its ingest URL. Add that URL as a webhook receiver in the Alertmanager that VictoriaMetrics (vmalert) sends its alerts to. The snippet beside this is the receiver configuration, with {{WEBHOOK_URL}} replaced by your real URL.

VictoriaMetrics (vmalert) cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.

CallHeim includes a payload mapping for VictoriaMetrics (vmalert)’s webhook format.

VictoriaMetrics (vmalert) documentation →

Setup snippetvictoriametrics
# Alertmanager config (vmalert sends its alerts to this Alertmanager with -notifier.url):
receivers:
  - name: callheim
    webhook_configs:
      - url: "{{WEBHOOK_URL}}"
        send_resolved: true
Check VictoriaMetrics (vmalert)’s current documentation for the exact fields.

After it arrives

What CallHeim does with VictoriaMetrics (vmalert) alerts.

Threshold alerts flap at the boundary. Where a source sends a recovery event CallHeim recognizes, a series that changes state four times inside ten minutes is grouped instead of re-paging, and the underlying incident stays open and visible.

CallHeim maps VictoriaMetrics (vmalert)’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point VictoriaMetrics (vmalert) at CallHeim and see what it does with your alerts.

Start on the free trial, connect VictoriaMetrics (vmalert) and send a test alert to see the incident it opens.