Agent Resolved Issues
Key | Product | Summary | Severity Level | Affected Version(s) | Release Version | Release Date |
---|---|---|---|---|---|---|
DBMON-11401 | Database Agent | Database Agent cannot to connect to the Oracle Real Application Clusters (Oracle RAC). | Medium | 25.7.0 | 25.9.0 | October 8, 2025 |
DBMON-10783 | Database Agent | Database data is not displayed on the Database Monitoring dashboard. | Medium | 24.10.0 | 25.9.0 | October 8, 2025 |
DBMON-11218 | Database Agent | Database Agent reports the value in the first row for User Processes Blocked (min) instead of adding the value in all rows. | Medium | 25.4.0 | 25.9.0 | October 8, 2025 |
DBMON-10807 | Database Agent | (MSSQL) The Database Memory used percentage metric value is not accurate. | Medium | 24.11.0 | 25.9.0 | October 8, 2025 |
SIM-10132 | Machine Agent | Machine Agent 25.7 with Docker Visibility does not collect and report container metrics. | Medium | 25.7.0 | 25.9.0 | September 30, 2025 |
SIM-10101 | After upgrading the Machine Agent to Java 17, excessive TRACE-level log errors are observed. | Medium | 25.6.0 | 25.9.0 | ||
SIM-10145 | Machine Agent 25.7 with Docker Visibility and Server Visibility enabled does not report metrics for all containers. | Medium | 25.7.0 | 25.9.0 | ||
CLUSTERMON-5976 | Cluster Agent | The Cluster Agent log file is frequently logging warning and error messages. | Medium | 25.6.0 | 25.9.0 | October 3, 2025 |
CLUSTERMON-5919 | Cluster Agent | The auto-instrumentation using the enableForceReInstrumentation parameter does not apply the configMap changes in all the deployments | Medium | 25.6.0 | 25.9.0 | October 3, 2025 |
JAVA-14116 | Java Agent | Java Agent does not monitor JMX attributes if the attributes repeatedly return null values. | Medium | 25.7.0 | 25.9.0 | October 16, 2025 |
JAVA-14115 | Java Agent fails to start on WebLogic 14.x after upgrading your Java application from version 8 to 11. | 25.8.0 | ||||
JAVA-14106 | Java Agent fails to start on webMethods 10.15 when you set the appagent.start.timeout setting in the config.ini file. | 24.3.0 | ||||
JAVA-14113 | Java Agent fails to monitor business transactions when you enable HTTP2 on a Spring WebFlux application that uses Reactor Netty. | 25.8.0 | ||||
JAVA-14103 | Java Agent receives large number of TSS requests and results in unexpected issues. | 25.8.0 | ||||
JAVA-14122 | Java Agent does not retry when it receives an OK response without a container ID, which impacts the application monitoring. | 25.2.0 |