Installling and Configuring Application Analytics for PCF

This document describes how to configure an analytics agent and view Application Analytics on the AppDynamics controller.

Feature Snapshot

If your AppDynamics controller has a license for analytics monitoring, you can monitor application analytics.

Step 1: Install and Configure AppDynamics Application Analytics for PCF

  1. In the Settings tab, click AppDynamics Analytics Agent Configuration.

  2. Paste in the Analytics Controller, Account Name, Global Account Name, and Access Key from the AppDynamics Controller license page. Make sure analytics support is included in the license. License Page

  3. Under Analytics Events HTTP Endpoint, enter the AppDynamics Analytics Event Service URL if you already have one. If you do not have one, contact AppDynamics support. The Analytics Event Service SaaS version URL is in the following format: http://analytics-event-service.com:80. The URLs will be slightly different depending on if you’re implementing a SaaS or On-premises solution.

  4. Click Save.

  5. After the tile updates successfully, get the route of the AppDynamics Analytics application by running the command:

    $ cf target -o appdynamics-org api endpoint: https://api.sys.pie-20.cfplatformeng.com api version: 2.103.0 user: admin org: appdynamics-org space: appdynamics-space

    $ cf apps Getting apps in org appdynamics-org / space appdynamics-space as admin... OK

    name requested state instances memory disk urls appdanalytics-4.5.545 started 1/1 1G 1G appdanalytics.cfapps.pie-multi-az-blue.cfplatformeng.com appdnozzle-4.5.555 started 1/1 1G 1G appdnozzle.cfapps.pie-multi-az-blue.cfplatformeng.com appdpcfdashboard-4.5.555 started 1/1 128M 1G appdpcfdashboard.cfapps.pie-multi-az-blue.cfplatformeng.com appdservice-4.5.551 started 1/1 256M 1G appdservice.cfapps.pie-multi-az-blue.cfplatformeng.com spring-music started 1/1 1G 1G spring-music-zany-jaguar.cfapps.pie-multi-az-blue.cfplatformeng.com started 3/3 1G 1G spring-music-quick-hedgehog.cfapps.pie-20.cfplatformeng.com

Step 2: Bind the Application to the Analytics Agent

After deploying the tile, follow the steps below to bind an application with the analytics agent to collect analytics data.

Note: The analytics agent only works with Java, .NET, and Node.js applications.

  1. Set a Java system property on the application to forward data to the analytics agent.

    $ cf set-env TARGET-APP-NAME JAVA_OPTS "-Dappdynamics.analytics.agent.url=http://appdynamics-analytics.DOMAIN-NAME/v1/sinks/bt"
    In the example above, appdanalytics.cfapps.pie-20.cfplatformeng.com is the URL of the analytics agent running in the AppDynamicsPCFOpsMetrics-service-org organization.

  2. Restage the application for the changes to take effect.

    $ cf restage TARGET-APP-NAME

Step 3: Configure Controller to Fetch Data from Event Service

  • For customers using SaaS controllers: Your controller is already configured to fetch data from a SaaS event service.
  • For customers using an on-premises controller: Log in to your controller as an admin and configure the event service URL and controller key for authentication.

For help with this configuration, contact AppDynamics support.

Step 4: Configure Analytics Collector on the Controller

On your AppDynamics controller, to configure the analytics collector for a target application:

  1. Click Analytics. ConfigureAnalyticsCollector

  2. From the Configure Analytics for Applications dropdown, choose the same target application for which you set the Java system property in the previous step.

  3. Select the checkbox to enable Analytics Data Collection for PCF.javaApp.

  4. Select which transactions you want to report analytics data. enter image description here

  5. (Optional) Configure the HTTP Data Collectors and Transactions for GUID Injection fields. For more information, see the AppDynamics documentation:

    • Configure HTTP Data Collectors: This enables collection of additional business data using HTTP data collectors.
    • Configure Transactions for GUID Injection: By configuring business transactions for GUID injection, you can correlate logs to specific business transaction requests. This can be helpful when you see slow transactions and the call graph does not give you enough information to get to the root cause. You can use this feature to get the full context related to a failed or slow transaction. Optional Fields
Create a pull request or raise an issue on the source for this page in GitHub