AppDynamics Integration
Overview
AppDynamics provides deep application performance monitoring (APM) and infrastructure visibility.
To integrate AppDynamics with our platform, we use an HTTP Request Template. Instead of sending AppDynamics' default complex payload, we use Velocity Template Language (VTL) to extract only the necessary variables. This formats the outgoing webhook to perfectly match our Event âž” Alert âž” Incident workflow.
Provider Configuration & Mapping
AppDynamics sends event severity as ERROR, WARN, or INFO. We map these specific text values to our platform's internal priorities.
Priority Mapping Config:
JSON
{
"priority": {
"field": "$.Severity",
"options": [
{ "value": "ERROR", "label": "Error" },
{ "value": "WARN", "label": "Warning" },
{ "value": "INFO", "label": "Info" }
],
"mapping": {
"ERROR": "CRITICAL",
"WARN": "MEDIUM",
"INFO": "LOW"
}
}
}Correlation (Fingerprint): We use $.IncidentNumber, which pulls from the AppDynamics ${latestEvent.id}. This unique ID allows our platform to track the alert and automatically resolve it when AppDynamics sends a recovery signal.
Setup Instructions
Step 1: Get Your Webhook URL
Log in to your alert management platform.
Go to Sources → Add Source.
Select AppDynamics as your provider.
Save the configuration and copy the https://api.itoc360.app/functions/v1/events URL.
Step 2: Create the HTTP Request Template
Log in to your AppDynamics Controller.
From the top navigation bar or left menu, click Alert & Respond.
Click HTTP Request Templates.
Click New to create a fresh template.

Step 3: Configure the Request Settings
Fill out the configuration form with your webhook details:
Name: Type a clear name (e.g.,
OnCall Platform Webhook).Method: Select
POST.Authentication: Leave this as
NONE.

Under the Custom Request Headers section, click Add Header:
Header Name:
Content-TypeHeader Value:
application/json
Under the Payload section:
MIME Type: Select
application/json.Paste the following VTL-formatted JSON into the text area:
JSON

Under the Settings section:
Check the box for One Request Per Event. This ensures alerts are sent individually and not batched together.
Click Save.

Step 4: Test the Template
Scroll to the bottom of your saved template and click Test.
Click Add Event Type and select an event like Health Rule Violation Started - Warning.
Click Run Test.

A green SUCCESS status indicates the payload was successfully delivered to your platform.

Step 5: Create an Action
After testing the template, you must save it as an executable Action.
Go back to the Alert & Respond menu and click Actions on the left sidebar.
Click Create Action.
Select Make an HTTP Request and click OK.

Name: Type a name for this action (e.g.,
OnCall Platform Webhook).HTTP Request Template: Select the template you created in Step 3 from the dropdown menu. The URL and Payload will auto-populate.
Click Save.

Step 6: Link the Action to a Policy
To automate the webhook, you need to attach this Action to a monitoring Policy. When the policy triggers an alert, it will execute the webhook.
In the Alert & Respond menu, click Policies.
Click Create Policy. (If a setup wizard appears, click Create Policy Manually under Quick Links).

In the Trigger tab, define which events should trigger the alert. For example, check the boxes for Health Rule Violation Events (Warning, Critical, etc.).

You should choose;
Health Rule Violation Started - Critical
Health Rule Violation Started - Warning
Health Rule Violation Ended - Critical
Health Rule Violation Ended - Warning
Go to the Actions tab at the top.
Click the + button to select an action. Choose your newly created
OnCall Platform Webhookaction and click Select.

Click Save to activate the policy. You will now see your active policy properly linked to the webhook action.

Last updated
Was this helpful?

