APM & tracing
Send AppDynamics alerts to on-call with CallHeim.
Alert & Respond HTTP Request Action (policy violations). CallHeim maps the payload, collapses repeats within five minutes, and pages whoever is on call for the service it belongs to.
Set the payload template first
Without a custom payload template on the AppDynamics side, it sends an empty or differently shaped body that CallHeim cannot map. Set the template shown below before pointing a monitor at this integration.
Setting it up
Create an Integration in CallHeim and choose AppDynamics from the Catalog. You get an ingest URL for that integration — paste it into AppDynamics’s webhook configuration. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.
If you enable request signing on this integration, CallHeim requires a valid HMAC-SHA256 signature in the X-ItOnCall-Signature or X-Hub-Signature-256 header on every request to it. Without a signing secret, the ingest URL itself is the credential.
CallHeim includes a payload mapping for AppDynamics’s webhook format, built and tested against sample payloads.
# AppDynamics → Alert & Respond → HTTP Request Templates → New
# URL: {{WEBHOOK_URL}} Method: POST Payload: application/json
# Include policyName, severity, eventType, incidentId, summaryMessage, application.name.After it arrives
What CallHeim does with AppDynamics alerts.
Trace and service alerts often arrive in bursts when one dependency degrades. Repeats of the same alert collapse onto one incident inside a five-minute window, and alerts from the same source whose titles share most of their words are grouped onto a still-unacknowledged incident within ten minutes — word overlap, not root-cause analysis.
CallHeim maps AppDynamics’s own severity to a P1–P5 level and shows a separate, explainable severity suggestion — a published keyword ruleset plus your own resolved-incident history — 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 →
CallHeim closes an incident on a recovery event only for sources whose recovery payload it recognises (or that you map). For the others, a person resolves the incident.
The thresholds it passes through
- Dedup window
- 300s
- 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 window and the flap settings are fixed. How alerts are processed →
Point AppDynamics at CallHeim and see what it does with your alerts.
Explore the platform, connect one source, and send yourself a test page by e-mail (early access).
Early access · every workspace starts with a 14-day trial for up to 5 seats, no card required