AppDynamics Integration

You can configure AppDynamics to post data to Moogsoft when actions of interest occur. See docs.appdynamics.com for details on AppDynamics components.

The following video introduces the basic process for creating an AppDynamics webhook for user with Moogsoft

Before You begin

This integration was validated with the AppDynamics Controller build 20.8.1-3791 on September 18, 2020.

Before you start to set up your integration, ensure you have met the following requirements:

  • You have an active AppDynamics account.

  • You have the necessary permissions to create alerts and HTTP request templates in AppDynamics.

  • You know how to define alerts in AppDynamics.

  • AppDynamics can make requests to external endpoints over port 443. This is the default.

Define the HTTP Request Template in AppDynamics

Do the following:

  1. Click Alert & Respond (top menu) and then HTTP Request Templates (left menu).

  2. Create a new request template. Specify the settings as defined below:

    • Request URL

      • Method = POST

      • Raw URL = The events endpoint shown in the Moogsoft web UI > Data Config > Ingestion Services > Events API page

        Events_URL.png

      • URL Encoding = UTF-8

    • Custom request headers

      Add the following headers:

      • Content-Type = application/json

      • apiKey = your-API-token-key

        For information on generating a Moogsoft API key, see Managing API Keys.

    • Response handling criteria

      Each HTTP request template must include the following. For more information about alerts and HTTP request templates, see docs.appdynamics.com.

      Your template should handle the following status codes.

      • Failure criteria: 400, 401, 405, 406

      • Success criteria: 200, 202

      For the 200 status code, specify the following:

      • Expect Payload enabled

      • Content Type = application/json

    • Settings

      Disable One Request Per Event and leave the other settings at their defaults.

    • Payload

      In the Payload section, do the following:

      1. Set the Mime Type to application/json and Payload Encoding to UTF-8.

      2. Specify the payload you want to send in the Payload field.

      The following script shows an example payload with AppDynamics variables included. You can copy and paste this script into the Payload field.

      Download example script

      Note the following:

      • Only the source, severity, description, check, and service fields are required.

      • The tags value enables you to specify custom data that is not defined in the standard schema.

      • If AppDynamics variables do not provide the values you want, use the following workarounds as needed:

        • Specify hard-coded strings for the values of interest.

        • Use event workflows to enhance new alerts with relevant data from your production environment.

  3. Add this template to all AppDynamics policies you want to observe in Moogsoft. See Configure the Monitoring Policy in AppDynamics below.

Configure the Monitoring Policy in AppDynamics

In AppDynamics, choose Alert & Respond (top) and then Policies (left).

For each policy that you want to observe in Moogsoft, do the following.

Event triggers

In the Trigger tab:

  • Check the Enabled and Execute actions in batch options.

  • Enable all the event triggers that you want to observe in Moogsoft;

Actions

In the Actions tab, add the HTTP request template you just defined to the Actions to Execute tab.

In this section: