Download PDF
Download page Deploy Analytics Without the Analytics Agent.
Deploy Analytics Without the Analytics Agent
Deployment Support
In this context, "agentless" refers to the configuration of Transaction Analytics without an Analytics Agent. An app server agent, such as Java or .NET, is still required to use this feature.
Agentless Analytics
To capture Transaction Analytics for Java or .NET Windows applications, you can configure Transaction Analytics without a dedicated Analytics Agent.
In this deployment model, Analytics retrieves data directly from your app agent. The data is reported to the Events Service and then the Controller. No separate Analytics Agent is required.
If you upgrade the Java Agent to >= 4.5.15, and use Transaction Analytics, Agentless Analytics is automatically enabled. If you upgrade the .NET Agent to >= 20.10, and use Transaction Analytics, Agentless Analytics is automatically disabled; you can enable this feature in the Controller or with a node property. See Enable Agentless Analytics.
You may notice unusual behavior (such as gaps in Analytics data) related to two known issues:
- High CPU usage (in the Java Agent version 4.5.19 and below)
- Blocked firewall requests
Requirements
Make sure you meet the following minimum requirements:
Sufficient Transaction Analytics Licenses
- Java Agent >= 4.5.15
- .NET Agent >= 20.10
- Controller >= 4.5.16 (SaaS or on-premises)
To use Agentless Analytics, see this compatibility matrix for your agent deployment requirements.
Minimum Controller Version | Minimum Java Agent Version | Agentless Analytics Support |
---|---|---|
4.5.16 | 4.5.15 | Generally available. |
4.5.16 | 4.5.17 | Supports proxy configuration and authentication with encrypted credentials. |
4.5.17 | 4.5.18 | Supports license rules configured in the Java Agent. |
Minimum Controller Version | Minimum .NET Agent Version | Agentless Analytics Support |
---|---|---|
4.5.16 | 20.10.0 | Generally available and supports proxy configuration. |
4.5.17 | 20.10.0 | Supports license rules configured in the . NET Agent. |
Connect App Agents to the Events Service
See the following sections to ensure that your deployment can connect to the Events Service:
Identify Internal Events Service Endpoints
The Controller uses the connection URL configured in Admin.jsp
to the Events Service. Agentless Analytics also uses this URL. See Connect to the Events Service.
In an on-premises environment, the agent requires access to the internal Events Service URL normally used by the Controller. The internal Events Service URL must be exposed to the agents and then set as the analytics.agentless.event.service.url
:
- Log in to the Administration Console:
http:<controller-hostname>:8080/controller/admin.jsp
orhttps:<controller-hostname>:45/controller/admin.jsp
. - In Controller Settings, set
analytics.agentless.event.service.url
to the Events Service endpoint that is accessible from agents. - Click Save.
Connection Ports
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.
Enable SSL
If you use a custom trust store, see Enable SSL for the Java Agent or Enable SSL for the .NET Agent.
Proxy Configuration
The .NET Agent does not support proxy authentication. Use these environment variables for proxy configuration.
To configure the .NET Agent to communicate with the Events Service with the proxy:
- Add/update the following environment variables.
- Restart your Windows application.
Agent → Events Service Sending Data For Proxy |
---|
|
appdynamics.http.proxyPort |
Enable Agentless Analytics
You can enable Agentless Transaction Analytics at the Controller, node/tier, and agent level.
By default, Agentless Analytics is disabled for the .NET Agent. Enabling Agentless Analytics changes your deployment to Agentless Analytics mode.
To enable Agentless Analytics at the tier or node level, add the agentless-analytics-disabled
property and set to false
. When set to false
, this node property changes the tier/node to Agentless Analytics mode. To add a node property, see App Agent Node Properties.
Disable Agentless Analytics
You can disable Agentless Transaction Analytics at the Controller, node/tier, and agent level.
Disabling Agentless Analytics changes your deployment to Analytics Agent mode.
To disable Agentless Analytics at the tier or node level, add the agentless-analytics-disabled
property and set to true
. When set to true
, this node property reverts the tier/node to Analytics Agent mode. To add a node property, see App Agent Node Properties.
By default, Agentless Analytics is disabled for the .NET Agent. Enabling Agentless Analytics changes your deployment to Agentless Analytics mode.
To disable Agentless Analytics, set the value of agentless-analytics-disabled
to true
.
Override the Events Service URL
To override the Events Service URL in the Java Agent, use the appdynamics.analytics.agent.agentless.es.url
property. When this property is set, the Java Agent will ignore the Events Service URL received from the Controller and use the URL from the property to publish events.
This property is supported in Java Agent version >= 22.3.0.
To override the Events Service URL in the .NET Agent, use appdynamics.analytics.agent.agentless.es.url
. When this environment variable is set, the .NET Agent will ignore the Events Service URL received from the Controller and use the URL from the environment variable to publish events.
This environment variable is supported in .NET Agent version >= 22.5.0.
Existing Analytics Agents
Once you upgrade to the minimum Controller and agent versions, existing Analytics Agents stops reporting data. Agentless Analytics does not duplicate data from the Analytics Agent. AppDynamics recommends when you see Transaction Analytics in the Controller, you can uninstall the Analytics Agent unless you are using Log Analytics.