This page describes the deployment options for Analytics, which includes the Events Service.
Transaction Analytics Only
The Analytics Agent is only required for the Node.js and PHP Agents, and not the Java and .NET Agents if the minimum versions are met. You need an Analytics Agent to capture Transaction Analytics for:
- Any version of Node.js Agent
- Any version of PHP Agent
- Java Agent <= 4.5.15
- .NET Agent <= 20.10
To configure Transaction Analytics:
Log Analytics Only
To configure Log Analytics:
Transaction and Log Analytics
To configure Transaction and Log Analytics:
SaaS/On-premises Analytics Configuration
When you deploy Analytics with the Analytics Agent, the configuration requirements differ based on your deployment.
- SaaS: 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 need to install only the Analytics Agent components of the system described in Agent Side Components.
- On-premises: You host the components yourself, storing all data on-premises. You need to install the Agent Side Components, Controller Deployment Components, and Events Service Deployment Components. While the on-premises deployment involves additional setup and administration, you are able to retain the Analytics data in your own data center.
Encrypt Data on the Analytics Agent
You can encrypt any data on the Analytics Agent using secure://<your-encrypted-credentials>
. You can encrypt data in the Analytics Agent properties file or in System Properties.
The following example demonstrates how to encrypt http.event.accessKey
in the Analytics Agent properties file.
http.event.accessKey=secure://-001-24-Dr9FQGC179o4vPnuljnx8A==ZGVw/P4OONvpUidIhJ2u78FpRVVW8fbgr8J1HBHXwnE=
ad.secure.credential.store.filename=/opt/appdynamics/secretKeyStore
ad.secure.credential.store.password=s_gsnwR6+LDch8JBf1RamiBoWfMvjjipkrtJMZXAYEkw8=
XML
See
Encrypt Agent Credentials.
Separate Host for the Analytics Agent
If your Analytics Agent is on a host separate from the monitored application, see Remote Analytics Agent Sizing.