Agent Resolved Issues
| Key | Product | Summary | Severity Level | Affected Version(s) | Release Version | Release Date |
|---|---|---|---|---|---|---|
| DBMON-11015 | Database Agent | Upgraded the Java Agent base image to jre17. | High | - | 25.4.0 | May 2, 2025 |
| DBMON-11006 | Database Agent | Database Agent does not collect data for Microsoft SQL Server database. | High | 25.1.0 | 25.4.0 | May 2, 2025 |
| DBMON-11003 | Database Agent | Database Agent displays an error while processing the InnoDB metrics in MySQL database. | Medium | 25.1.0 | 25.4.0 | May 2, 2025 |
| DBMON-10878 | Database Agent | Database Agent does not connect to the Microsoft SQL Server database if the collector is configured using the Windows authentication. | Medium | 25.1.0 | 25.4.0 | May 2, 2025 |
| DBMON-10805 | Database Agent | Database Agent creates multiple processes on the database server. | Medium | 24.11.0 | 25.4.0 | May 2, 2025 |
| DOTNET-7464 | .Net Agent | The agent stops working when instrumenting a .NET 6+ application with preload enabled and IIS automatic configuration turned off. | Medium | 25.2.0 | 25.4.0 | May 9, 2025 |
| DOTNET-7493 | .Net Agent | Sometimes, the MIDC Data Collectors fail to gather data from asynchronous methods. This happens due to a race condition in task instrumentation, where multiple tasks or threads access and change shared data at the same time without proper synchronization. | Medium | All versions | 25.4.0 | May 9, 2025 |
| DOTNET-7494 | .Net Agent | The agent Docker image cannot be deployed in OpenShift and Kubernetes environment. | Medium | 25.2.0 | 25.4.0 | May 9, 2025 |
| JAVA-13874 | Java Agent | The Controller randomly drops some events. This happens because the agent sends excessive number of events to the Controller. | Medium | 24.8.0 | 25.4.0 | May 8, 2025 |
| JAVA-13935 | Java Agent | In distributed asynchronous transactions, the agent may mistakenly classify all transaction segments as entry points for analytics. This can lead to the selection of an incorrect segment for capturing a snapshot. | Medium | 25.1.0 | 25.4.0 | May 8, 2025 |
| JAVA-13922 | Java Agent | The Java Agent auto-instrumentation fails because the agent extracts container ID even when containerAppCorrelationMethod is set to none. | High | 25.1.0 | 25.4.0 | May 8, 2025 |
| PHP-2666 | PHP Agent | The PHP agent reports segmentation faults when the Method Invocation Data Collector (MIDC) is enabled. This impacts agent performance and leads to the loss of analytics data. | Medium | 24.4.0 or higher | 25.4.0 | May 14, 2025 |
| PHP-2680 | PHP Agent | In the install.sh script, a proxy flag automatically launches the proxy that overrides other proxy settings. | Medium | 24.11.0 | 25.4.0 | May 14, 2025 |
| WEBSRV-1252 | Apache Web Server Agent | The agent proxy does not start using the command line option. | - | 24.11.0 | 25.4.0 | April 14, 2025 |
| WEBSRV-1257 | Apache Web Server Agent | The PHP Agent does not report to Controller when Apache Agent is instrumented with PHP Agent using the mod_php module. | - | 23.x, 24.x | 25.4.0 | April 14, 2025 |
| SERVER-9907 | Machine Agent | When the agent starts as a service on Linux, it records an error in the startup logs. This happens because the log4j2 settings are not properly configured. | Medium | 24.9.0 | 25.4.0 | April 30, 2025 |
| SERVER-9903 | Machine Agent | JVM crash guard does not work on Windows. | Medium | 24.12.0 | 25.4.0 | April 30, 2025 |
| SERVER-9884 | Machine Agent | Some JRE files that are bundled with agent include incorrect permissions. | Medium | 24.10.0 | 25.4.0 | April 30, 2025 |
| SERVER-9874 | Machine Agent | Grok pattern for log analytics displays an error message in the Controller UI. This issue occurs when using the Analytics Agent image bundled with Machine Agent. | Medium | 25.1.0 | 25.4.0 | April 30, 2025 |
| SERVER-9825 | Machine Agent | The agent shows memory and CPU usage data that do not match the actual server data. | Medium | 24.10.0 | 25.4.0 | April 30, 2025 |
| SERVER-9824 | Machine Agent | The HP-UX agent produces an incorrect collector script, where the JSON output is missing the closing (}) character. This causes problems when debugging the script output. | Low | 24.10.0 | 25.4.0 | April 30, 2025 |
| SERVER-9725 | Machine Agent | The agent does not report all /dev volumes. | Medium | 24.8.0 | 25.4.0 | April 30, 2025 |