Generic webhook
Send OpenTelemetry / CloudEvents alerts to on-call with CallHeim.
CloudEvents 1.0 structured-mode JSON events (Knative, Azure Event Grid, or your own CloudEvents producer). This is not an OpenTelemetry (OTLP) receiver. 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
Each CloudEvent’s id is unique, so repeats of the same problem collapse only if you put a stable value in data.dedupKey.
Create an Integration in CallHeim and choose OpenTelemetry / CloudEvents from the Catalog. You get an ingest URL for that integration, which you paste into OpenTelemetry / CloudEvents’ 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.
OpenTelemetry / CloudEvents 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 OpenTelemetry / CloudEvents’ webhook format.
# POST a CloudEvents 1.0 structured event:
curl -X POST "{{WEBHOOK_URL}}" \
-H 'content-type: application/cloudevents+json' \
-d '{"specversion":"1.0","id":"...","source":"...","type":"...",
"subject":"...","data":{"message":"...","severity":"critical","dedupKey":"<stable id for this alert>"}}'After it arrives
What CallHeim does with OpenTelemetry / CloudEvents alerts.
Anything that can POST a JSON object can raise an alert. A no-code mapping (dot and bracket paths — a JSONPath subset, not the full spec) picks out the fields you care about, and the alert joins the same pipeline as every cataloged source.
CallHeim maps OpenTelemetry / CloudEvents’ 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 →
Point OpenTelemetry / CloudEvents at CallHeim and see what it does with your alerts.
Start on the free trial, connect OpenTelemetry / CloudEvents and send a test alert to see the incident it opens.