Logging

Send Papertrail alerts to on-call with CallHeim.

Saved-search alert webhook (log events). 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.

papertrailSolarWindssource names also accepted: paper-trail

Needs a forwarder

Papertrail does not post to CallHeim on its own for this. You set up a forwarder, rule or script that sends the event to your CallHeim URL; the setup steps show what to send.

Batched deliveries

Papertrail can send several matching log lines in one delivery. CallHeim opens one alert for the whole delivery, with the match count in the body.

Setting it up

Papertrail sends its JSON inside a form field named payload (application/x-www-form-urlencoded), and CallHeim’s ingest URL takes a JSON body. Add a small relay that reads the payload field and POSTs the JSON to your CallHeim integration URL.

Create an Integration in CallHeim and choose Papertrail from the Catalog to get its ingest URL, and use that URL as the target of your forwarder. CallHeim’s ingest URL takes a JSON request body. The snippet beside this shows the request it expects, with {{WEBHOOK_URL}} replaced by your real URL.

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

Papertrail documentation →

Setup snippetpapertrail
# Papertrail → Search → Save Search → Edit Alert → Webhook
# URL: <your relay URL>
# The relay reads the "payload" form field and POSTs the JSON it holds to {{WEBHOOK_URL}}.
Check Papertrail’s current documentation for the exact fields.

After it arrives

What CallHeim does with Papertrail alerts.

Log-derived alerts carry long, near-identical titles. A repeat of the same alert attaches to its open incident (within 24 hours of the incident opening unless the sender supplies its own dedup key), and alerts with closely similar titles from the same source can be grouped onto one open, unacknowledged incident within ten minutes, at a title similarity of at least 0.6.

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

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