APM & tracing

Send New Relic alerts to on-call with CallHeim.

Alerts / Workflows webhook (incidents & issues). 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.

newrelicsource names also accepted: new-relic, new relic, nr

New Relic alerts become CallHeim alerts: repeats of the same incident collapse onto one CallHeim incident, and the service the integration is bound to pages whoever is on call for it. CallHeim includes a payload mapping for New Relic’s webhook format. New Relic ships two alerting shapes — classic Alerts and the newer Workflows — and CallHeim reads both.

How the alert reaches on-call

  1. Step 1A New Relic alert condition (classic) or a Workflow (current) opens an issue.
  2. Step 2New Relic POSTs a JSON body to your CallHeim ingest URL through a webhook destination.
  3. Step 3CallHeim reads the incident or issue id as the identity signal and maps severity or priority to CallHeim's scale.
  4. Step 4A repeat of 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 a Webhook destination in Alerts > Destinations.

    Create the New Relic integration in CallHeim first to get the exact ingest URL, and paste it into the destination.

  2. 02

    Set the authentication, if any.

    New Relic's webhook destination offers Basic Auth or a bearer token — not an arbitrary named header, so HMAC signing to CallHeim's exact header is usually not available here.

  3. 03

    Create (or edit) a Workflow that uses the destination.

    Filter the workflow by the policy or tag you want paged, and attach the webhook destination as its channel.

Example payloadJSON
{
  "incident_id": 987654,
  "condition_name": "Apdex < 0.7 on web-store",
  "details": "Apdex score dropped to 0.55 over 5 minutes",
  "severity": "CRITICAL",
  "current_state": "open",
  "policy_name": "web-store-prod",
  "incident_url": "https://alerts.newrelic.com/accounts/1/incidents/987654"
}
Example payload in New Relic's classic Alerts webhook format; check New Relic's own documentation for the Workflows payload if you use that shape instead.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
title (Workflows) / condition_name / policy_nameincident title
priority (Workflows: CRITICAL/HIGH/MEDIUM/LOW) or severity (classic: CRITICAL/WARNING/INFO)severityCRITICAL→P1, HIGH→P2, WARNING or MEDIUM→P3, INFO or LOW→P4.
details / issuePageUrl / incident_url / descriptionincident body
issueId (Workflows) or incident_id (classic)identity signalcurrent_state is not read, so a close event does not change the identity.

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 New Relic's own issueId or incident_id, so the same open issue re-notifying collapses, at any age, because the id is New Relic's own key. While the incident is open, a repeat of the same issue that attaches to it does not page again.

Recovery

When New Relic sends a closed notification, CallHeim records it against the incident: current_state is read on classic alert payloads and state on Workflows payloads. Close a test issue from your own workflow to see the result in your organization before you rely on it.

Troubleshooting

Common problems and how to fix them
ProblemFix
A closed New Relic incident leaves the CallHeim incident open.Check that the delivered body carries current_state: closed (classic) or state: CLOSED (Workflows); a custom template that renames the field is not read. If it still stays open, resolve it in CallHeim.
Severity always lands at P3.Neither priority nor severity was present in the delivered body — check the destination is attached to a workflow with the right notification template.
HTTP 400 on send.A custom Handlebars payload template on the destination produced invalid JSON — preview it in New Relic before saving.
No alerts arrive.Confirm the workflow's filter actually matches the policy or tag the issue was opened under.
HTTP 401 once you enabled signing.New Relic's webhook destination supports only Basic Auth or a bearer token, not an arbitrary header name, so it cannot send X-CallHeim-Signature. Leave signing off.

Security

New Relic's webhook destination supports Basic Auth or a bearer token, not a named custom 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 New Relic at CallHeim and see what it does with your alerts.

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