Agent Resolved Issues
| Key | Product | Summary | Severity Level | Affected Version(s) | Release Version | Release Date |
|---|---|---|---|---|---|---|
| NETVIZ-84 | Network Agent | Network AgentThe Network Agent fails to properly handle a large number of Java Agents in a containerized environment. See . | High | 24.9.0 | 25.5.0 | May 2, 2025 |
| NETVIZ-98 | Network Agent | The default flowgroup_limit is not configurable, leading to the error ERROR ip_flowgrp_lookup: flowgrp alloc failed. | - | - | 25.5.0 | May 26, 2025 |
| NETVIZ-103 | Network Agent | The Network Agent does not report metrics for OpenShift containers. | - | - | 25.5.0 | May 26, 2025 |
| COSMOSX-2430 | Smart Agent | The existing Smart Agent is not removed during an upgrade, causing the Smart Agent to be unresponsive. | Medium | - | 25.5.0 | May 29, 2025 |
| COSMOSX-2434 | Smart Agent |
The application metrics are not displayed and Controller displays the 500 internal server error. This release fixes the issue with clean up of sockets on Windows machines. | Medium |
| 25.5.1 | June 3, 2025 |
| CLUSTERMON-5662 | Cluster Agent | Auto-instrumentation of a Java application fails when you use the manual app correlation and thecontainerAppCorrelationMethod is set to none. | Medium | 25.3.0 | 25.5.0 | June 2, 2025 |