Authentication

This provider requires authentication.
  • appDynamicsAccountName: AppDynamics Account Name (required: True, sensitive: False)
  • appId: AppDynamics appId (required: True, sensitive: False)
  • host: AppDynamics host (required: True, sensitive: False)
  • appDynamicsAccessToken: AppDynamics Access Token (required: False, sensitive: False)
  • appDynamicsUsername: Username (required: False, sensitive: False)
  • appDynamicsPassword: Password (required: False, sensitive: True)
Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:
  • authenticated: User is Authorized (mandatory)
  • administrator: Administrator privileges (mandatory)

In workflows

This provider can’t be used as a “step” or “action” in workflows. If you want to use it, please let us know by creating an issue in the GitHub repository.

Connecting with the Provider

  1. Ensure you have a AppDynamics account with the necessary permissions. The basic permissions required are Account Owner or Administrator. Alternatively you can create an account instructions

Provider configuration

  1. Find your account name here.
  2. Get the appId of the Appdynamics instance in which you wish to install the webhook into.
  3. Determine the Host here.

Basic Auth authentication

  1. Obtain AppDynamics Username and Password
  2. Go to Basic Auth tab under Authentication section
  3. Enter Username and Password
Keep add AppDynamics Username and Password

Access Token authentication

  1. Log in to the Controller UI as an Account Owner or other roles with the Administer users, groups, roles permission.
  2. Go to Administration
AppDynamics Administration
  1. Go to API Client tab
AppDynamics API Client tab
  1. Click + Create
Create new AppDynamics API Client
  1. Fill Client Name and Description
  2. Click Generate Secret
AppDynamics generate API Client Secret
This API Client secret is not an authentication token yet
  1. Add Account Owner and/or Administrator roles
AppDynamics add API Client roles
  1. Click Save
AppDynamics save API Client
  1. Click Generate Temporary Token
AppDynamics Generate API Client Temporary Access Token
This token is not persistent, but since Keep uses it just once to install Webhook, we will use it without oAuth
  1. Click Save one again
This is important. Otherwise generated token will not be saved and authentication will fail
  1. Copy generated token
AppDynamics copy API Client Temporary Access Token
  1. Go to Access Token tab under Authentication section
Keep add AppDynamics Access Token
  1. Enter Access Token

Connecting provider

  1. Ensure Install webhook is checked
  2. Click Connect

Webhook Integration Modifications

The webhook integration adds Keep as an alert monitor within the AppDynamics instance. It can be found under the “Alerts & Respond” section. The integration automatically gains access to the following scopes within AppDynamics:
  • administrator
  • authenticated