Uptime & synthetics
Send Uptime Kuma alerts to on-call with CallHeim.
Self-hosted uptime monitoring — heartbeat webhooks. 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.
Setting it up
Create an Integration in CallHeim and choose Uptime Kuma from the Catalog. You get an ingest URL for that integration, which you paste into Uptime Kuma’s webhook configuration. CallHeim’s ingest URL takes a JSON request body. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.
Uptime Kuma 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 Uptime Kuma’s webhook format.
# Uptime Kuma → Settings → Notifications → Add → Webhook
# Post URL: {{WEBHOOK_URL}}
# Body includes {heartbeat:{status (0=down,1=up), msg}, monitor:{name}}.After it arrives
What CallHeim does with Uptime Kuma alerts.
Repeated failures from the same probe attach to the incident already open for that check: at any age when the tool sends its own check id, and within 24 hours of the incident opening when only the check name identifies it. Failures with different titles from the same source can still be grouped onto an open, unacknowledged incident within ten minutes, when the sender does not supply its own dedup key.
CallHeim maps Uptime Kuma’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 →
If Uptime Kuma sends a recovery notification, CallHeim records it against the incident.
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 →
Point Uptime Kuma at CallHeim and see what it does with your alerts.
Start on the free trial, connect Uptime Kuma and send a test alert to see the incident it opens.