In this context, "agentless" refers to the configuration of Transaction Analytics without an Analytics Agent. An app server agent, such as the Java Agent or the .NET Agent, is still required to use this feature.
Agentless Analytics Overview
If you want to capture Transaction Analytics for Java or .NET applications, you can configure Transaction Analytics without a dedicated Analytics Agent on Windows.
In this deployment model, Analytics retrieves data directly from your app agent. The data is reported to the Events Service and then the Controller. Therefore, no separate Analytics Agent is required.
If you upgrade the Java Agent to version 4.5.15 and later and use Transaction Analytics, Agentless Analytics is automatically enabled. If you upgrade the .NET Agent to version 20.10 and later and use Transaction Analytics, Agentless Analytics is automatically disabled.
You may notice unusual behavior (such as gaps in Analytics data) related to two known issues:
- High CPU usage
- Blocked firewall requests
Make sure you meet the following minimum requirements:
Sufficient Transaction Analytics Licenses
- Java Agent version 4.5.15 and later
- .NET Agent version 20.10 and later
- Controller version 4.5.16 and later (SaaS or on-premises)
Some deployments have different agent requirements to use agentless Transaction Analytics and connect to the Events Service. The Java and .NET Agents differ in their deployments. For example, the .NET Agent does not support proxy authentication with encrypted credentials, but supports proxy configuration.
The table below provides a summary of Agentless Analytics support.
|Minimum Controller Version
|Minimum Java Agent Version
|Minimum .NET Agent Version
|Agentless Analytics Support
|Supports proxy authentication with encrypted credentials.
|Supports license rules configured in the Java or .NET Agent.
SaaS vs On-Premises Deployments
Agentless Analytics is available for both SaaS and on-premises deployments. All configuration requirements are identical for both deployment types.
Connect App Agents to the Events Service
For most deployments, communication between the Java Agent, .NET Agent, and Events Service automatically occurs as long as you have the correct agent version. See the appropriate documentation to ensure that your deployment can connect to the Events Service.
Identify Internal Events Service Endpoints
AppDynamics uses connection URLs to connect the Events Service to the Controller and app agents. The URL used for the Controller-Events Service connection may be different than the URL used for the app agent-Events Service connection. For example, SaaS deployments use internal URLs for the Controller-Events Service connection.
If your deployment uses different URLs for each connection, you need to provide the Controller-Events Service URL as an administrator property. This allows your app agent to find the Events Service endpoint.
To connect the app agent to an internal Events Service URL:
- Log in to the administration console:
http:<controller-hostname>:8080/controller/admin.jsp or https:<controller-hostname>:45/controller/admin.jsp.
- In Controller Settings, navigate to the
analytics.agentless.event.service.urlproperty and input your Controller-Events Service endpoint.
- Press Save.
For SaaS-based installations, the connection between the Java Agent, the .NET Agent, and the Events Service takes place over ports 80 (HTTP) and 443 (HTTPS). If your firewall rules are not configured properly, gaps will appear in your Analytics data.
For on-premises installations, the port on which the Events Service receives data from the Java Agent and the .NET Agent is configured during installation.
If you have network policies that may prevent this connection, such as firewalls, you need to configure the policies to connect with the Events Service. See Troubleshoot Analytics Issues.
Proxy Authentication with Encrypted Credentials
If you encrypts credentials for proxy authentication, you need Java Agent 4.5.17 and later and Controller 4.5.17 and later. See Java Agent Configuration Properties.
The .NET Agent does not currently support proxy authentication with encrypted credentials; it supports proxy configuration. See .NET Agent Configuration Properties.
|Agent → Events Service Sending Data For Proxy
If you created license rules for the Java Agent, you need Java Agent 4.5.18 and later and Controller 4.5.17 and later.
For license rules for the .NET Agent, you need .NET Agent 20.10 and later and Controller 4.5.17 and later.
Adjust Configuration Properties
The Java Agent can be configured to handle higher loads if necessary. Contact AppDynamics Support to tune these properties.
Enable Agentless Analytics
By default, Agentless Analytics is disabled for the .NET Agent.
To enable Agentless Analytics for the .NET Agent, see Enable Transaction Analytics Without an Analytics Agent.
Disable Agentless Analytics
By default, Agentless Analytics is enabled for the Java Agent.
To disable Agentless Analytics for the Java Agent, see Disable Transaction Analytics Without an Analytics Agent.