Installing and Configuring Application Analytics for Pivotal Platform
The diagram illustrates the analytics agent that is installed by the tile and a Pivotal Platform app microservice-1 that is running the AppDynamics APM agent and forwarding transaction analytics events to the Analytics Agent. The Pivotal Platform app is configured to include an environment variable to direct the transaction analytics events to the analytics agent, based on the Analytics Agent’s route in the Pivotal Platform environment. The parameters required by the Analytics Agent to communicate with the AppDynamics events service are entered in the tile.
If your AppDynamics controller has a license for analytics monitoring, you can monitor application analytics.
In the Settings tab, click AppDynamics Analytics Agent Configuration.
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.
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.
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
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.
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.comis the URL of the analytics agent running in the AppDynamicsPivotal PlatformOpsMetrics-service-org organization.
Restage the application for the changes to take effect.
$ cf restage TARGET-APP-NAME
- 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.
On your AppDynamics controller, to configure the analytics collector for a target application:
From the Configure Analytics for Applications dropdown, choose the same target application for which you set the Java system property in the previous step.
Select the checkbox to enable Analytics Data Collection for Pivotal Platform.javaApp.
Select which transactions you want to report analytics data.
(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.
Check the logs for the analytics agent
appdanalytics-<version> in the Apps Manager
under appdynamics-org/appdynamics-space to confirm there are no communication issues
with the configured AppDynamics events service.
If a Pivotal Platform app is configured to forward transaction analytics events to the Analytics Agent, they should appear in the Controller under Analytics.