Security

Send Auth0 alerts to on-call with CallHeim.

Log Streams webhook — tenant auth events (failed logins, blocks). 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.

auth0Okta (Auth0)source names also accepted: auth-zero

Setting it up

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

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

Auth0 documentation →

Setup snippetauth0
# Auth0 → Monitoring → Streams → Create Stream → Custom Webhook
# Payload URL: {{WEBHOOK_URL}}   Content Type: application/json
# Content Format: JSON Object. CallHeim reads one JSON object per delivery, so JSON Lines and JSON Array do not work.
# Each log event is {log_id, data:{type, description, ip, user_name}}.
Check Auth0’s current documentation for the exact fields.

After it arrives

What CallHeim does with Auth0 alerts.

A repeat of the same finding attaches to the incident already open for it, and an Orchestration Rule can route findings by severity, title or any payload field to the team that owns them.

CallHeim maps Auth0’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 →

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 Auth0 at CallHeim and see what it does with your alerts.

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