Cloud platforms

Send Azure Monitor alerts to on-call with CallHeim.

Alerts via action group webhook (Common Alert Schema). 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.

azuremonitorsource names also accepted: azure, azure-monitor

Setting it up

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

Azure Monitor 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 Azure Monitor’s webhook format.

Azure Monitor documentation →

Setup snippetazuremonitor
# Azure Portal → Monitor → Alerts → Action groups → Create
# Add action: Webhook → enable "Common alert schema"
# URI: {{WEBHOOK_URL}}
Check Azure Monitor’s current documentation for the exact fields.

After it arrives

What CallHeim does with Azure Monitor alerts.

Each platform or account event is mapped to the service the integration is bound to. A repeat of the same event (the same rule and resource, event ARN, alert instance or policy incident, depending on the source) attaches to the open incident, and the provider’s own grouping is not carried over. An Orchestration Rule can route or re-prioritize by fields in the event.

CallHeim maps Azure Monitor’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 Azure Monitor 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 Azure Monitor at CallHeim and see what it does with your alerts.

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