On this page:
Application Analytics is built on top of the AppDynamics platform, including the Events Service, the unstructured document store for the platform. The exact components you need to install and the steps for doing so depend upon your environment and your requirements. This section outlines some of those considerations and scenarios.
SaaS or On-Premises?
The first deployment question you need to consider is whether to use SaaS or On-Premises AppDynamics Analytics.
With SaaS, AppDynamics stores the data and hosts the server components of the system for you. In the on-premises approach, you host the components yourself, storing all data on-premises. These differences are:
- For SaaS, you need to install only the application agent components of the system, as described in Agent Side Components.
- For On-Premise, you need to install the Agent Side Components and the Controller and Events Service components described in Install the Controller and Install the Events Service. The on-premises deployment involves additional setup and administration, but it enables you to retain all analytics data within your own data center.
Agent Side Components
Whether you are using SaaS or On-premises Application Analytics, you need to deploy (or enable) components that provide Analytics functionality to the parts of the system that reside in your application environment. These appear on the left side of the diagram.
As numbered, the agent components are:
AppDynamics App Agent: Application Analytics relies upon the same app agents that AppDynamics APM uses. If you already use AppDynamics APM, you likely already have these deployed to your monitored applications.
that collects transaction and log data from .NET applications running on Windows OS.
For SaaS-based installations, the connection between the Agent and the Events Service in the cloud takes place over ports 80 (HTTP) and 443 (HTTPS). For on-premises installations, the port on which the Events Service receives data from the Agent is configured during installation.
Analytics Plugin (AP) to the App Agent: The Analytics Plugin extends App Agent functionality so that it can collect and forward data to the Analytics Agent. It is built into the 4.0 version of the Java and .NET App Agents, but is not enabled by default. No additional download is needed here.
Deploying Analytics Agents to Multiple Nodes
A real world scenario is unlikely to consist of a single monitored node, as shown in the diagram above. It usually consists of many applications deployed over many hosts.
While the APM app agents continue to send data to the Controller in the normal way, the Analytics Plugin, sends its data to the Analytics Agent component. This component runs in a separate JVM process in the local environment or network, either as part of the Standalone Machine Agent or on its own.
There must be at least one Analytics Agent in the monitored environment, although multiple agent plugins collecting only transaction data can share a single Analytics Agent, as shown in the figure. However, each machine where you want to gather log data must have its own Standalone Machine Agent with the Analytics Agent enabled.
In this example, AppServerHost1-3 are collecting only transaction data, so only app agents are required. Each one connects to the Analytics Agent on AppServerHost4, where log information is also being collected. The Analytics Agents could also reside on the same machines as each app agents. On AppServerHost5, only log data is being collected, so an Analytics Agent is also necessary there.
Server Side Components for On-Premise
To set up AppDynamics Analytics on-premise, you also need to install the server parts of the system, the AppDynamics Controller and the Events Service.
The following figure depicts the basic components of an On-premises deployment:
The server components add the following to the deployment:
AppDynamics Controller: The heart of an AppDynamics deployment, the Controller processes and presents the information gathered by the agents.
Events Service: The unstructured document store, it gathers and stores data from the Analytics Agents and, if you have End User Monitoring, from the EUM Server. It allows the Controller UI to run queries on that data.
If you are using SaaS EUM, you must use the SaaS Events Service. If you are using the on-prem EUM Server, you must use an on-premises instance of the Events Service.
Deployment Options Summary
To summarize the scenarios, when planning your deployment, consider the following:
- Are you implementing Application Analytics as a SaaS or an on-premises solution?
- For SaaS, the Events Service is provided as part of the SaaS service.
- For on-premises, the Controller and the Events Service must be installed on-premises as well.
- For each monitored machine, are you capturing log data, transaction data, or both?
- For log data only, install either the Standalone Machine Agent (Java) or the Analytics Agent (.NET) on the host and enable the App Agent Plugin.
- For log data and transaction data, install either the Standalone Machine Agent (Java) or the Analytics Agent (.NET) on the host and enable the App Agent Plugin.
- For transaction data only, install either the Standalone Machine Agent (Java) or the Analytics Agent (.NET) on each host or use a common Analytics Agent instance that is shared. Enable the App Agent Plugin on each host.
The following topics describe how to install the components:
- Installing Agent Side Components: You need to perform these steps whether you are using the on-premises or the SaaS form of the Application Analytics product.
- Install the Controller and Install the Events Service: You only need to perform these steps if you want your installation to be fully on-prem.