Agent Resolved Issues

Note:

Refer to the Agent Enhancements section of the release notes for general product updates and library changes. For security alerts requiring manual intervention (primarily for on-premises deployments), visit the Splunk Security Advisory portal.

Key Product Summary Severity Level Affected Version(s) Release Version Release Date
PHP-2713 PHP Agent The Analytics Agent displays the 'Request contains invalid data or illegal arguments' error message because of an incorrect JSON payload from the PHP Agent. Medium 25.10.0 26.4.0 May 13, 2026
PHP-2732 PHP Agent Frequent segmentation faults occur in Apache HTTPD child processes when PHP Agent is deployed with Drupal applications on RHEL using PHP 8.3 in Kubernetes. Medium 25.10.0 26.4.0 May 13, 2026
SYNTH-12177 Private Synthetic Agent Private Synthetic Agent in a Kubernetes environment fails to post synthetic monitoring results to the Controller. This issue is specific to certain recent versions of Kubernetes. High - 26.4.1 May 08, 2026
SIM-10408 Machine Agent The Machine Agent fails to report Load, Availability, Network, and Process metrics, while CPU, Memory, Volume, and Partition metrics continue to report as expected. High 25.12.0 26.4.0 May 08, 2026
SIM-10443 Machine Agent An error occurs when you select Specific Servers on the Create Health Rule page. Critical - 26.4.0 May 08, 2026
SIM-10506 Machine Agent When you run Analytics Agent and Machine Agent together in Kubernetes, both use the same environment variable for the access key, causing a conflict that prevents Analytics Agent from functioning correctly, if a non-default access key is set for the Machine Agent.

Resolution:

To resolve this conflict, use the APPDYNAMICS_AGENT_DEFAULT_ACCOUNT_ACCESS_KEY environment variable to specify the access key for the Analytics Agent. Continue to use APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY for the Machine Agent to ensure that each agent uses its respective, independent access key.

High - 26.4.0 May 08, 2026
SIM-10521 Machine Agent The Machine Agent installation on Windows fails because the JRE folder is unavailable in the build. High 26.3.0 26.4.0 May 08, 2026
JAVA-14389 Java Agent The Java Agent fails to instrument the latest version of Informatica (10.5.8). High 26.1.0 26.4.0 May 06, 2026
JAVA-14417 Java Agent Java Agent and JDK 17.0.17 compatibility issue results in duplicate class definition errors. Medium 26.1.0 26.4.0 May 06, 2026
JAVA-14469 Java Agent Java Agent fails to report servlet-based Business Transactions after upgrading MuleSoft to 4.9.12. High 26.2.0 26.4.0 May 07, 2026
PYTHON-1910 Python Agent After upgrading to Python Agent 26.4, the dl-proxy container is generating exception errors. As a result, the applications cannot start. Medium 26.4.0 26.4.1 April 30, 2026
CLUSTERMON-6348 Cluster Agent The Openshift OperatorHub includes incorrect documentation links. Medium 26.3.0 26.4.0 April 30, 2026
CLUSTERMON-6226 Cluster Agent Cluster Agent displays incorrect CPU %Busy metrics for pods with unspecified CPU limits. Medium 25.12.0 26.4.0 April 30, 2026
COSMOX-3066 Smart Agent Smart Agent fails to install or upgrade the Machine Agent to version 26.3.0.5242 on Linux and Windows, halting the operation while the Smart Agent remains operational. High 26.3.0 26.4.0 April 29, 2026
COSMOSX-3061 Smart Agent Smart Agent fails to return descriptive error messages when Machine Agent downloads fail during install or upgrade processes. Medium 26.3.0 26.4.0 April 29, 2026
DBMON-11651 Database Agent MongoDB Atlas database collectors fails to report first order metrics due to permission issue. Medium 25.10.0 26.4.0 April 28, 2026
DBMON-11733 Database Agent There is a mismatch between the number of monitored databases and the total Database license units consumed for MongoDB. This fix may result in an upward correction in license consumption. Medium 26.1.0 26.4.0 April 28, 2026
DBMON-11703 Database Agent Database Agent incorrectly reports blocking session events as warnings after the critical threshold has elapsed. Medium 25.10.0, 26.1.0 26.4.0 April 28, 2026
DBMON-11680 Database Agent Database Agent fails to connect to DB2 database when the agent runtime is Java 11. Medium 26.1.0 26.4.0 April 28, 2026
DBMON-11670 Database Agent When installed as a Windows service, the Database Agent is registered as Appdynamics instead of the expected Appdynamics Database Agent. Medium 26.1.0 26.4.0 April 28, 2026
NETVIZ-497 Network Agent The Network Agent generates alerts when the network monitoring system reports high packet drop rates. Medium 26.1.0 26.4.0 April 21, 2026
LIBAGENT-860 C/C++ SDK When you upgrade C/C++ SDK, the SSL handshake fails due to certificate verification failure causing HTTP request errors and agent configuration failures. High 25.8.0 26.4.0 April 22, 2026
LIBAGENT-861 C/C++ SDK The C++ SDK causes temporary loss of monitoring data and delays reporting. It may also trigger connection errors related to security certificates. Medium 25.8.0 26.4.0 April 22, 2026