Installing and Configuring AppDynamics for VMware Tanzu

This topic describes how to install and configure Splunk AppDynamics APM for VMware Tanzu.

The diagram illustrates the results of installing the tile. A Splunk AppDynamics service broker is deployed as a VMware Tanzu application to the org and space appdynamics-org/appdynamics-space. Each Controller configured in the tile is published to the Splunk AppDynamics marketplace service as a unique plan, which apps can bind to.

In addition, the tile publishes the Splunk AppDynamics extension buildpack, appdbuildpack, which supports multiple buildpack workflows.

Points to Consider

Starting with v4.5.545, Splunk AppDynamics Analytics support has been moved to a separate tile on VMware Tanzu Network. If you want to use Transactional Analytics, install Splunk AppDynamics Analytics for VMware Tanzu.
Starting with v4.7, the APM tile supports two options for configuring the Account Access Key used to communicate with the Controller. In order to use the obfuscated Account Access Key Secret field. We recommend that users update both the APM tile and the Splunk AppDynamics buildpack to version 4.7.x or higher, and the Java buildpack to version 4.19.2 or higher. With versions previous to 4.19.2 of the Java buildpack or 4.7 of the Extension Buildpacks, use the unobfuscated Account Access Key field. Starting with version 5.0 of the APM tile, the unobfuscated field is deprecated and will be removed.
The use of the obfuscated Access Key Secret field will change how the Account Access Key is represented in VCAP_SERVICES. Any app bound to an Splunk AppDynamics marketplace service will need to use an updated buildpack to consume the new field (at restage). Node.js apps should be upgraded to use the Extension Buildpack, or change the require statement to reference the updated field.

Before You Begin

Create a VMware Tanzu Network account if you do not have one.

Configuring SSL

If you are planning to use SSL, do the following based on the Controller type.

SSL for Splunk AppDynamics Controllers

The Controller uses DigiCert Global Root CA. The tile automatically imports the DigiCert Global Root CA into the keystore used by the Machine Agent and the dashboard app, if present.
Enable the SSL checkbox in the Machine Agent configuration.

SSL for Splunk AppDynamics On-Premises Controllers

For OnPremise Controller deployments, upload the root certificate for the internal CA that signed the Controller certificate for your OnPremise Controller in the security configuration of the BOSH Director.

For an example, see Security Page in the VMware Tanzu documentation.

Make sure to follow the exact format below while entering multiple certificates.

 —–BEGIN CERTIFICATE—– ABCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678AB EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF GH12345678ABCDEFGH12345678ABCDEFGH12345678… ——END CERTIFICATE—— —–BEGIN CERTIFICATE—– BCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABB EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF GH12345678ABCDEFGH12345678ABCDEFGH12345678… ——END CERTIFICATE—— —–BEGIN CERTIFICATE—– CDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABBB EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF GH12345678ABCDEFGH12345678ABCDEFGH12345678… ——END CERTIFICATE——

BASH

Set Up the APM Tile

Log in to Ops Manager.
If the Splunk AppDynamics Service Broker tile does not appear in the Installation Dashboard, click Import a Product in the left-side menu and import the Splunk AppDynamics tile.
Double-click the AppDynamics tile in the Installation Dashboard.

Controller Setup

In the Settings tab, click AppDynamics Controller Configuration. Then click Add.
Enter the following Service Plan options. All of these fields are required.
- Controller Configuration Name – A user-friendly name for this configuration profile. This name should include the Controller to which the Standalone Machine Agent reports.
- Controller Configuration Description – A more complete description of this configuration profile.
- Account Name – The account name used to access the Controller. You must specify an account with a valid App Agent license. To check this, do the following:
  - In the Controller, click the gear icon (top right) and choose License > Account > License.
  - In the Account Usage tab, under APM Usage, verify that the account has at least one available license unit for the type of application you are monitoring (Java, .NET, etc.).
- Account Key Information – Input controller access key in only one of these fields.
  - Account Access Secret (Recommended) – Hidden field to take in controller access key information
  - Account Access Key (Soon to be Deprecated) The account access key used to authenticate with the Controller. In the Controller, click the gear icon (top right) and choose License > Account > Access Key. Starting with Version 4.7.x, the APM tile supports two options for configuring the Account Access Key. We recommend that users update both the APM tile and the buildpack to version 4.7.x or higher, and the Java buildpack to version 4.19.2 or higher, in order to use the obfuscated Account Access Key Secret field. With versions previous to 4.19.2 of the Java buildpack or 4.7 of the Extension Buildpacks, use the unobfuscated Account Access Key field. The unobfuscated field is deprecated and will be removed starting from version 5.0 of the APM tile."
- Controller Host – The host name or the IP address of the Controller. Example values are 192.168.1.22 or myhost or myhost.example.com. This is the same host that you use to access the Splunk AppDynamics browser-based user interface. For an on-premises Controller, use the value for Application Server Host Name that was configured when the Controller was installed. If you are using the Controller service, see the welcome email from Splunk AppDynamics.
- Controller Port – The HTTP (unencrypted) port used to access the Controller web interface. Defaults are 8090 (on-premise Controllers) and 80 (SaaS Controllers).
- SSL Port – The HTTPS (encrypted) port used to access the Controller web interface. Defaults are 8181 (on-premise Controllers) and 443 (SaaS Controllers).
You can add multiple controller configurations by repeating steps 4 and 5. This will enable applications to bind to any of the entered configurations.
Click Save to save the changes and return to the Installation Dashboard.

Validating the Install

Once the tile install completes successfully in the Ops Manager, you can confirm that the Controller plans have been successfully installed using cf marketplace:

$ cf marketplace -s appdynamics
…
service plan description free or paid
my-controller1 controller1 free
…

CODE

Confirm that the extension buildpack is available by using cf buildpacks:

$ cf buildpacks
buildpack position enabled locked filename
…
appdbuildpack 24 true false appdynamics_buildpack-v4.6.13.zip

CODE