Metrics & monitoring

Send Grafana Mimir alerts to on-call with CallHeim.

Mimir Alertmanager pointed directly at CallHeim. CallHeim maps the payload, collapses repeats within five minutes, and pages whoever is on call for the service it belongs to.

mimirGrafana Labsalso accepts: grafana-mimir

Alertmanager groups

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 Grafana Mimir from the Catalog. You get an ingest URL for that integration — paste it into Grafana Mimir’s webhook configuration. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.

If you enable request signing on this integration, CallHeim requires a valid HMAC-SHA256 signature in the X-ItOnCall-Signature or X-Hub-Signature-256 header on every request to it. Without a signing secret, the ingest URL itself is the credential.

CallHeim includes a payload mapping for Grafana Mimir’s webhook format, built and tested against sample payloads.

Grafana Mimir webhook documentation →

Setup snippetmimir
# Mimir Alertmanager config (per-tenant):
receivers:
  - name: callheim
    webhook_configs:
      - url: "{{WEBHOOK_URL}}"
        send_resolved: true
Example shape written by us; check Grafana Mimir’s current documentation.

After it arrives

What CallHeim does with Grafana Mimir alerts.

Threshold alerts flap at the boundary. Where a source sends a recovery event CallHeim recognises, 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 Grafana Mimir’s own severity to a P1–P5 level and shows a separate, explainable severity suggestion — a published keyword ruleset plus your own resolved-incident history — 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 →

CallHeim closes an incident on a recovery event only for sources whose recovery payload it recognises (or that you map). For the others, a person resolves the incident.

The thresholds it passes through

Dedup window
300s
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 window and the flap settings are fixed. How alerts are processed →

CallHeim

Point Grafana Mimir at CallHeim and see what it does with your alerts.

Explore the platform, connect one source, and send yourself a test page by e-mail (early access).

Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required