APM & tracing

Send AppDynamics alerts to on-call with CallHeim.

Alert & Respond HTTP Request Action (policy violations). 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.

appdynamicssource names also accepted: appd, app-dynamics, cisco-appdynamics

Set the payload template first

AppDynamics posts to your CallHeim URL, but it only sends the fields you put in its payload template. Without one it sends an empty or differently shaped body that CallHeim cannot map, so set the template described in the setup steps before you point an alert 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, which you paste into AppDynamics’ webhook configuration. CallHeim’s ingest URL takes a JSON request body. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.

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

AppDynamics documentation →

Setup snippetappdynamics
# AppDynamics → Alert & Respond → HTTP Request Templates → New
# URL: {{WEBHOOK_URL}}   Method: POST   Payload: application/json
# Include policyName, severity, eventType, incidentId, summaryMessage, application.name.
Check AppDynamics’ current documentation for the exact fields.

After it arrives

What CallHeim does with AppDynamics alerts.

Trace and service alerts often arrive in bursts when one dependency degrades. 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 from the same source whose titles share most of their words are grouped onto one still-unacknowledged incident within ten minutes.

CallHeim maps AppDynamics’ 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 →

If AppDynamics sends a recovery notification, CallHeim records it against the incident.

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

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