View Source

Related pages:

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, PHP Agents, and Python 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
Python Agent >= 21.10 (Python Agent < 21.10 does not support Transaction Analytics)
Java Agent <= 4.5.15
.NET Agent <= 20.10

To configure Transaction Analytics:

Download and install either the 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:

Install either the Machine Agent or the Analytics Agent (standalone binary) on the machine.
Enable Analytics for log sources in the Controller.

Transaction and Log Analytics

To configure Transaction and Log Analytics:

Install either the Machine Agent or the Analytics Agent (standalone binary) on the machine.
Enable Analytics for applications and log sources in the Controller.

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. 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.

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.