AppDynamics Integration Guide
Logo | Company | Estimated Time | Functionality | Vendor Docs |
---|---|---|---|---|
![]() | AppDynamics | 30 minutes | One-Way | --- |
AppDynamics Integration
AppDynamics provides application and database performance management, monitoring, and analytic tools to help you identify and resolve performance issues, drive business outcomes, increase user engagement, and deliver amazing web user experiences.
How AppDynamics users benefit from PagerTree
AppDynamics triggers user defined events by monitoring applications. PagerTree acts as the dispatcher for these events, determining the right people to notify based on on-call schedules. PagerTree notifies them via email, sms, voice, and/or push notifications until the alert is acknowledged or closed.
Functionality of Integration
The AppDynamics integration is one-way, meaning:
- When a monitor event is triggered (
event_type === "trigger"
) in AppDynamics, an alert is created in PagerTree automatically. - When a monitor event is resolved (
event_type === "resolve"
) in AppDynamics, the incialertdent is resolved in PagerTree automatically.
Tutorial Overview
In this integration tutorial we will show you how to send alerts from AppDynamics into PagerTree. The estimated time for this integration is 30 minutes. We assume that you already have a PagerTree and AppDynamics account setup.
In PagerTree
- From the action button, click the “Create Integration” button.
- In the “Create Integration” box, fill out the following:
- Name of the Integration.
- Select the Type to AppDynamics
- Select an appropriate Urgency for when this integration is triggered
- Select the Team this alert will be assigned to
- Click Save
- Copy the Endpoint URL
In AppDynamics
- Go to the Alert & Respond tab, then HTTP Request Templates, then click “+ New”
- In the “Create HTTP Request Template” box
- First Section
- Name the template appropriately (ex: “PagerTree Integration Template”)
- Custom Templating Variables
- Add 1 custom templating variable
- pt_event_type with value trigger
- pt_event_type with value trigger
- Add 1 custom templating variable
- Request URL Section
- Select Method as POST
- Paste the PagerTree Endpoint URL you copied for Raw URL
- Select URL Encoding as UTF-8
- Authentication Section
- Select Type as NONE
- Payload Section
- Select MIME Type as application/json
- Select Payload Encoding as UTF-8
- In the text area below Payload encoding, paste the below code
- Response Handling Criteria Section
- Under Success Criteria, click Add Success Criteria.
- Select 200 from the Status Code list
- Check Expect Payload checkbox
- Select application/json from the Content/Type list
- Under Success Criteria, click Add Success Criteria.
- Settings Section
- Check “One Request Per Event”
- Once your template is saved you can test it to make sure an alert is created in PagerTree. Click the Test button, then click Add Event Type and select an event you want to test (our example uses “Health Rule Violation Started – Warning”, but you can pick any event type), then click Run Test. If you executed all steps correctly, PagerTree should have created an alert and notified the team member on-call. If you see that PagerTree did not create an alert, scroll to the very bottom of the Test Transcript and check the Response Payload for any errors.
- Click Actions on the left menu, select an application or database to create actions for, then click “+ Create”
- Select Make an HTTP Request from the list and click OK.
- Give the action a Name (ex: “PagerTree Trigger”) and then select the template you just created from the list, then click Save.
- Create another action that will be used for resolving alerts. Give the action a Name (ex: “PagerTree Resolve”) and select the template you just created again. When the form populates, change the pt_event_type for this new action to resolve, then click Save.
- Lastly, we need to add these new actions to your desired policies. Click Policies on the left menu, and either edit or create a new policy.
- At the top of the Create Policy dialog box Name the policy (ex: “Critical or Warn”).
- On the Trigger Tab, check the conditions with “Health Rule Violation Started” in the name.
- On the Actions Tab, click the “+” button to add an action to execute. Name the policy (ex: “Critical or Warn”). Click the Trigger Action you recently created, and then click Select. In the Create Policy Dialog click Save.
- Create another policy that triggers when any conditions with “Health Rule Violation Ended” in the name. Assign the Resolve Action to this policy.
- Check “One Request Per Event”
- First Section
You have successfully completed the AppDynamics Integration. Now when AppDynamics creates an alert, PagerTree will create an alert and route it to the correct team member that is on-call. If you have any questions please contact support@pagertree.com