Uptime & synthetics

Send Healthchecks.io alerts to on-call with CallHeim.

Cron / heartbeat monitoring — fires when a check goes down. 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.

healthchecksiosource names also accepted: healthchecks, hc-io

Set the payload template first

Healthchecks.io posts to your CallHeim URL, but it only sends the fields you put in its payload template. Without one it sends an empty or differently shaped body that CallHeim cannot map, so set the template described in the setup steps before you point an alert at this integration.

Setting it up

Create an Integration in CallHeim and choose Healthchecks.io from the Catalog. You get an ingest URL for that integration, which you paste into Healthchecks.io’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.

Healthchecks.io 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 Healthchecks.io’s webhook format.

Healthchecks.io documentation →

Setup snippethealthchecksio
# Healthchecks.io → Integrations → Webhook
# POST URL: {{WEBHOOK_URL}}
# Body (JSON): {"name":"$NAME","status":"$STATUS","tags":"$TAGS"}
Check Healthchecks.io’s current documentation for the exact fields.

After it arrives

What CallHeim does with Healthchecks.io 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 Healthchecks.io’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 Healthchecks.io 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 →

CallHeim

Point Healthchecks.io at CallHeim and see what it does with your alerts.

Start on the free trial, connect Healthchecks.io and send a test alert to see the incident it opens.