In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
Choose this option if all alerts go to one channel. It’s the simpler setup.View dedicated integration setup steps
View dedicated integration setup steps
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration, and enter the integration page
- Choose AppDynamics integration and click Save to generate a card
- Open the generated integration card and copy the Push URL
Use a shared integration
Choose this option if you need to route alerts to different channels based on the alert payload.Configure in AppDynamics
1
Create an HTTP Request Template in AppDynamics
Where:AppDynamics › Alert & Respond › HTTP Request Templates › New
Payload:
Click Save.Special Note (Optional Configuration)Configuration:
If you need to configure

Payload:
Click Save.Special Note (Optional Configuration)Configuration: Custom Templating Variables
If you need to configure Custom Templating Variables, refer to the following JSON template. Here, custom_variables is a fixed format, and the variables within custom_variables are custom Variables. The names defined on the page must match the variable names referenced in the JSON template. These variables become labels of the same name on the Flashduty alert.2
Create an HTTP Action in AppDynamics
Where:AppDynamics › Alert & Respond › Actions › Create Action
-
Select
Actionsin the left navigation bar, choose the application type you want to create for, and clickCreate. -
In the
Create Actionpopup, selectMake an HTTP Requestand clickOK.
-
In the
Create HTTP Actionpopup, enter aName, select the Flashduty template created in the previous step as theHTTP Request Template, and clickSAVE.
3
Use the action in an alert policy
Where:AppDynamics › Alert & Respond › Policies
- Create or edit a policy (configure the alert rules as needed; that configuration is omitted here).
-
In the
Actionssection of the policy configuration page, click add and select the action created in the previous step.
-
In the policy’s triggers (Health Rule Violation Events), select the events for a violation ending (Ended) and being canceled (Canceled) as well as the ones for a violation starting. Flashduty decides recovery from
event_typein the notification: a type containingCLOSEorCANCELEDrecovers the matching alert. If you do not select these events, AppDynamics sends no recovery and the alert does not recover on its own. -
After completing other configurations, click
Save.
4
Trigger a health rule and verify
Cause a violation of a health rule covered by the policy (or wait for a real one). A few seconds later, the integration in Flashduty shows a Latest event time, which means the setup works; after the violation ends, confirm the matching alert recovers.
Status and severity
Alert Key and recovery
Flashduty usesincident_id from the payload as the Alert Key; if incident_id is still the unresolved ${latestEvent.incident.id}, it uses details.event_id instead. The alert recovers when details.event_type contains CLOSE or CANCELED. The alert title is “application name::event name”.