Configure the Controller Connection

There are two options to configure the Java Agent to connect to the Splunk AppDynamics Controller:

See Agent-to-Controller Connections.

Configure the Agent with the Kudu Console

When you add the Splunk AppDynamics Azure Site Extension to your web app, you can interactively configure the Java Agent using the Kudu Console.
  1. Navigate to the Splunk AppDynamics Controller Configuration page in the Kudu Console:
    http://{web app}.scm.azurewebsitesJava/appdynamics/
    For example: https://myazureexample.scm.azurewebsitesJava/appdynamics/
  2. On the Splunk AppDynamics Controller Configuration page, enter your Controller connection information.
    For example:
    • Controller Host: mycompany.saas.appdynamics.com
    • Port: 443
    • Select Enable SSL
    • Account Name: MyAccount
    • Access Key: <your access key from the Controller UI>
    • Application Name: MyAzureApp
  3. Click Validate to test the connection to the Splunk AppDynamics Controller and save your settings.
  4. Restart your web app.
    After you apply some load to your web app, you can view it on flow maps in the Splunk AppDynamics Controller UI.

Configure the Agent Using Environment Variables

Configuring the Java Agent using environment variables allows for unattended configuration. To configure agents, add the environment variables before you install the Splunk AppDynamics Azure Site Extension:
  1. Navigate to SETTINGS > Application Settings for your web app.
  2. Add the Java Agent environment variables under App settings:
    • APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY : A unique key associated with the Controller account.
    • APPDYNAMICS_CONTROLLER_HOST_NAME : The hostname of the Splunk AppDynamics Controller.
    • APPDYNAMICS_CONTROLLER_SSL_ENABLED : Set it to True to enable SSL connection to the Controller. Otherwise set it to False .
    • APPDYNAMICS_AGENT_ACCOUNT_NAME : The account name you use to log on to the Controller.
    • APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY : The account key you use to log on the Controller.
    • APPDYNAMICS_AGENT_APPLICATION_NAME : The business application name in the Controller.
    • APPDYNAMICS_AGENT_TIER_NAME : The tier name in the Controller.
    • APPDYNAMICS_AGENT_NODE_NAME : The node name in the Controller.
  3. Restart your web app.
    After you apply some load to your web app, you can view it on flow maps in the Splunk AppDynamics Controller UI.