APM & tracing

Send Dynatrace alerts to on-call with CallHeim.

Problem notifications via a custom integration webhook. 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.

dynatracesource names also accepted: dt

Dynatrace problem notifications become CallHeim alerts: repeats on the same problem 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 Dynatrace’s webhook format.

How the alert reaches on-call

  1. Step 1A Dynatrace problem opens or its state changes.
  2. Step 2Dynatrace's custom-integration problem notification renders your payload template and POSTs it to your CallHeim ingest URL.
  3. Step 3CallHeim reads the problem's PID as the identity signal and maps its ProblemImpact to a severity.
  4. Step 4A repeat on the same problem 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

    Add a problem notification integration in Dynatrace.

    Settings (classic) > Integration > Problem notifications > Add notification > Custom integration.

  2. 02

    Enter your CallHeim ingest URL and set a custom payload.

    Create the Dynatrace integration in CallHeim first to get the exact ingest URL. Dynatrace needs a body template — include PID, ProblemID, ProblemTitle, State, ProblemImpact, ImpactedEntity and ProblemDetailsText, since those are the fields the CallHeim parser reads.

  3. 03

    Send a test notification before saving.

    Dynatrace's own "Send test notification" button confirms the template renders valid JSON before it goes live.

Example payloadJSON
{
  "PID": "-1234567890123456789_PID",
  "ProblemID": "P-2026...",
  "ProblemTitle": "Failure rate increase on payment-service",
  "ProblemImpact": "SERVICE",
  "State": "OPEN",
  "ImpactedEntity": "payment-service",
  "ProblemDetailsText": "Failure rate increased to 8% in the last 5 minutes"
}
Example payload in the fields the template asks Dynatrace to send; check Dynatrace's own documentation for the full placeholder list.

What CallHeim reads from the payload

Payload fields and what each one maps to on the incident
Payload fieldMaps toNote
ProblemTitle / titleincident title
ProblemImpact (ENVIRONMENT / APPLICATION / SERVICE / INFRASTRUCTURE)severityENVIRONMENT or APPLICATION→P1, SERVICE→P2, INFRASTRUCTURE (or anything else)→P3, unless State is RESOLVED or CLOSED, which writes P4 instead. ProblemSeverity is not read.
ProblemDetailsText / ImpactedEntity / ProblemImpactincident body
PID (or ProblemID, or ProblemURL)identity signal

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 problem's PID (or ProblemID), so repeated notifications about the same problem collapse, at any age, because the id is Dynatrace's own key.

Recovery

Include State in the payload template. When Dynatrace sends a problem with State RESOLVED or CLOSED, CallHeim records it against the incident for that problem at severity P4. If an incident is still open after Dynatrace reports the problem resolved, resolve it in CallHeim.

Troubleshooting

Common problems and how to fix them
ProblemFix
A resolved problem stays open.Check that State is in the payload template and that Dynatrace sends a notification when the problem closes.
The body is empty.No custom payload template was set on the notification — Dynatrace sends nothing usable without one (see setup).
Every problem lands at P3.ProblemImpact was missing from the template; confirm it is included and spelled exactly as Dynatrace names it.
HTTP 400 on send.Curly-brace placeholders like {ImpactedEntities} and {ProblemDetailsJSON} are JSON data types in Dynatrace's template syntax and must not be wrapped in quotes — a quoted placeholder breaks the JSON once substituted.
HTTP 401 once you enabled signing.Dynatrace 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

Dynatrace's custom integration can send only fixed additional HTTP 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 Dynatrace at CallHeim and see what it does with your alerts.

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