Logging

Send Elastic / Kibana alerts to on-call with CallHeim.

Kibana alerting webhook connector (ELK rule alerts). 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.

elasticsource names also accepted: kibana, elasticsearch, elk

Set the payload template first

Elastic / Kibana 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.

Kibana alerting rules become CallHeim alerts: repeats on the same rule collapse onto one incident, and the service the integration is bound to pages whoever is on call for it. CallHeim includes a payload mapping for Elastic’s webhook format.

How the alert reaches on-call

  1. Step 1A Kibana alerting rule's condition matches and it runs its actions.
  2. Step 2Kibana's Webhook connector renders your body template with the rule's context and POSTs it to your CallHeim ingest URL.
  3. Step 3CallHeim reads the rule's id as the identity signal and maps a severity word from the rendered body.
  4. Step 4A repeat on the same rule attaches to the incident that is already open for it.
  5. Step 5The integration's bound service selects an escalation policy, which pages the on-call tier.

Setting it up

  1. 01

    Create a Webhook connector in Kibana.

    Stack Management > Connectors > Create connector > Webhook, or add it directly from a rule's Actions tab.

  2. 02

    Enter your CallHeim ingest URL.

    Create the Elastic integration in CallHeim first to get the exact ingest URL. Set authentication to none unless you need it for network access control on your side.

  3. 03

    Write a custom JSON body using Kibana's Mustache template syntax.

    Kibana requires a body for a webhook action — a bare connector sends nothing usable on its own. Template it from rule.id, rule.name, context.message, a severity value (severity or kibana.alert.severity), alert.id and alert.actionGroup (Mustache {{rule.id}}, {{alert.id}}, {{alert.actionGroup}}), since those are the fields the CallHeim parser reads.

  4. 04

    Add the connector as an action on the alerting rule.

    To send recoveries too, add the action for the Recovered action group as well.

Example payloadJSON
{
  "rule": { "id": "rule-77", "name": "CPU usage high" },
  "alert": { "id": "alert-1", "actionGroup": "query matched" },
  "severity": "critical",
  "context": { "message": "CPU usage is 95% on node-3" }
}
Example payload in the fields the body template asks Kibana to render; check Elastic's own documentation for the full context-variable list.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
rule.name / ruleName / nameincident title
severity / "kibana.alert.severity" (critical / high / medium / low)severitycritical→P1, high→P2, medium→P3, low→P4; alert.actionGroup of "recovered" overrides this to P4.
context.message / reason / messageincident body
rule.id (or ruleId), plus alert.id when sentidentity signalalert.id is added to the identity when the template sends it.

How CallHeim processes it

Routing

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged.

Deduplication

A repeat of the same alert attaches to the incident that is still open for it in the same service, triggered or acknowledged, with no new incident and no new page. When the sender supplies its own dedup key (a PagerDuty dedup_key, an Opsgenie alias, a Datadog alert id, an Alertmanager fingerprint, or a dedupKey that is more than the alert title), this holds however late the repeat arrives. When the identity comes from the e-mail subject or the alert title, the repeat attaches only if the incident was triggered in the last 24 hours; after that it opens a new incident and pages. A repeat at P1 or P2 is not folded into an open P3, P4 or P5 incident: it opens a new incident and pages. Once an incident is resolved or closed, the next repeat opens a new incident. Identity is the alerting rule's own id (plus alert.id when your template sends it), so repeated firings of the same rule collapse, at any age, because the id is Elastic's own.

Recovery

When Kibana runs the Recovered action group with alert.id in the body, CallHeim records it against the incident for that rule instance at severity P4. This needs alert.id and alert.actionGroup in the body template.

Troubleshooting

Common problems and how to fix them
ProblemFix
The body is empty or a template error.Kibana requires a JSON body template on a webhook action — a connector with no template sends nothing usable (see setup).
HTTP 400 on send.Mustache auto-escapes template variables; a raw quote inside context.message can still break the surrounding JSON if the template was not written carefully — preview it in Kibana before saving.
A recovered alert stays open.Check that the template sends alert.id and alert.actionGroup, and that the connector also runs on the Recovered action group.
Every alert lands at P3.Neither severity nor kibana.alert.severity was populated in the rendered body — check the template references one of them.
HTTP 401 once you enabled signing.Kibana cannot send a signature computed for each request. Remove the signing secret from this integration, or put a proxy you run in front that signs each request.

Security

Kibana's webhook connector can send only fixed custom headers, which cannot carry a signature computed for each request. The integration URL is the credential: keep it secret, and if it is exposed, disable the integration and create a new one. A signing proxy you run in front of the sender can add an X-CallHeim-Signature header; without one, do not set a signing secret, because every unsigned delivery would be rejected.

Vendor documentation checked

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

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