Incident & ITSM

Send FireHydrant alerts to on-call with CallHeim.

FireHydrant incident webhooks, brought in through a generic webhook integration with a field mapping. 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.

firehydrantsource names also accepted: fire-hydrant

Setting it up

FireHydrant nests the incident under data.incident. Create a generic webhook integration in CallHeim, add a field mapping that reads data.incident.name for the title, data.incident.severity.slug for the severity and data.incident.id for the dedup key, and point FireHydrant’s webhook at that integration’s URL.

Create a generic webhook integration in CallHeim to get an ingest URL, and paste it into FireHydrant’s webhook settings. The snippet beside this shows the settings, with {{WEBHOOK_URL}} replaced by your real URL.

FireHydrant 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.

FireHydrant documentation →

Setup snippetfirehydrant
# FireHydrant → Integrations → Webhooks → New
# URL: {{WEBHOOK_URL}} (the URL of a generic webhook integration with a field mapping)
# Field mapping: title = data.incident.name, severity = data.incident.severity.slug (add a severity map for SEV1 to SEV4), dedupKey = data.incident.id
Check FireHydrant’s current documentation for the exact fields.

After it arrives

What CallHeim does with FireHydrant alerts.

Incidents and tickets raised in another system can open an incident here for paging and escalation. A repeat carrying that system’s own identifier attaches to the incident already open for it, however long after the first. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages instead. CallHeim does not write status back to the source system.

CallHeim reads the severity from the field you send or map, 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 FireHydrant at CallHeim and see what it does with your alerts.

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