Error tracking

Send Sentry alerts to on-call with CallHeim.

Issue webhooks from a Sentry internal integration (or the legacy webhook plugin). 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.

sentrysource names also accepted: sentry.io

Sentry issues become CallHeim alerts: repeats on the same issue 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 Sentry’s webhook format.

How the alert reaches on-call

  1. Step 1An issue is created or resolved in Sentry.
  2. Step 2Sentry POSTs the issue webhook to your CallHeim ingest URL.
  3. Step 3CallHeim reads the issue's shortId as the identity signal and maps its level to a severity.
  4. Step 4A repeat on the same issue 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 an Internal Integration in Sentry, not a legacy plugin.

    Settings > Developer Settings > New Internal Integration. The legacy webhook plugin still works and CallHeim reads its flat payload shape too, but Sentry's own newer integration path is the internal integration.

  2. 02

    Enable the webhook and point it at your CallHeim ingest URL.

    Create the Sentry integration in CallHeim first to get the exact ingest URL. Enable the webhook, point it at that URL and tick the Issue resource, so created and resolved events are sent.

  3. 03

    Use the Issue resource webhook rather than an alert-rule action.

    A rule action ("Send a notification via <your integration>") sends a different body (data.event and data.triggered_rule), so subscribe the integration to the Issue resource instead.

Example payloadJSON
{
  "action": "created",
  "data": {
    "issue": {
      "id": "1234567890",
      "shortId": "WEB-STORE-42",
      "title": "TypeError: Cannot read properties of undefined",
      "culprit": "checkout(app/cart.js)",
      "level": "error",
      "permalink": "https://sentry.io/organizations/web-store/issues/1234567890/"
    }
  }
}
Example payload for an Issue resource webhook; check Sentry's own documentation for the full payload.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
data.issue.title / culpritincident title
data.issue.level (fatal / error / warning / info / debug)severityfatal→P1, error→P2 (also the default), warning→P3, info or debug→P4.
data.issue.culprit / metadata.value / permalinkincident body
data.issue.shortId (or id)identity signalThe stable per-issue id, not the per-event id — so repeated events on the same issue collapse instead of opening a new incident each time.

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 Sentry's own shortId (or numeric id) for the issue, so repeated events on one issue collapse regardless of how many times the underlying error fires. The issue id is Sentry's own key, so a repeat attaches at any age.

Recovery

When Sentry sends an issue webhook with the action resolved, CallHeim records it against the incident for that issue. Resolve a test issue in Sentry to see the result in your organization before you rely on it.

Troubleshooting

Common problems and how to fix them
ProblemFix
Nothing arrives when an issue is created.The Issue resource is not ticked on the integration, or the integration is not installed on the project.
Every event on an issue opens a new incident.Check the events are actually the same issue (same shortId) — a Sentry fingerprint change on the error creates a new issue with a new shortId.
The title is unhelpful ("Sentry issue").Neither title nor culprit was present in the payload; that usually means the legacy plugin shape was used with a message field instead.
HTTP 401 once you enabled signing.Sentry's internal integration does not expose a field for a custom outbound header; if yours does not either, leave signing off for this source.
Alerts land at P2 when they should not.error is also the fallback severity when level is missing or unrecognized — confirm the alert rule is actually populating level.

Security

Sentry's internal integration does not offer a field to add a custom outbound header. 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 Sentry at CallHeim and see what it does with your alerts.

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