Works with: 


Application Analytics deployment options vary based on several factors, such as which data you would like to monitor and your Controller deployment. This topic covers all of your options to deploy the Analytics Agent.

Transaction Analytics Only 

You need an Analytics Agent to capture Transaction Analytics for:

  • Java Agents version 4.5.15 and earlier
  • Any version of .NET, Node.js, and PHP Agents 
  • Controller version 4.5.15 and earlier 

To configure Transaction Analytics:

  • Download and install either the Standalone Machine Agent or the Analytics Agent (standalone binary) on each machine. You can also use a shared Analytics Agent instance.

  • Enable Analytics for applications in the Controller.

Log Analytics Only

To configure Log Analytics:

Transaction and Log Analytics

To configure Transaction and Log Analytics:

  • Install either the Standalone Machine Agent or the Analytics Agent (standalone binary) on the machine.

  • Enable Analytics for applications and log sources in the Controller.

SaaS vs On-premises Analytics Configuration

When you deploy Analytics with the Analytics Agent, the configuration requirements differ based on your deployment:

  • The Events Service is provided as part of the SaaS service. AppDynamics stores the data and hosts the server components of the system for you. You install only the Analytics Agent components of the system. This is described in the section Agent Side Components.
  • For on-premises, you host the components yourself, storing all data on-premises. This means you need to install the Agent Side Components and the Controller and Events Service components described in Controller Deployment and Events Service Deployment. The on-premises deployment involves additional setup and administration, but it enables you to retain the analytics data within your own data center.  

Separate Host for the Analytics Agent

If your Analytics Agent is on a host separate from the monitored application, see Remote Analytics Agent Sizing.