OneAgent 1.299 is the last version supporting OneAgent Extensions 1.0 framework. You can continue using OneAgent Extensions 1.0 if you stay at OneAgent version 1.299. Note that this means you'll be using an unsupported Python version 3.8. We strongly recommend migrating your extensions to the latest Extensions 2.0 framework.
For environments with Extensions 1.0, the OneAgent version 1.301 rollout starts after Oct 31, 2024.
Fixed an issue where the Java code module aborted capturing information from a servlet or filter, which could cause missing paths if there was an exception while obtaining the servlet path. (OA-35559)
Updated libexpat dependency to 2.6.3. (OA-36844)
Fixed an issue where some OneAgents completely stopped producing new paths after going through a very high load period. (OA-36727)
Fixed container group identifier (CG) calculation for Amazon ECS deployments. The `cluster` and `task-definition-family` are used to create the CG instead of the task ARN. (OA-35582)
.NET
Fixed an issue with the .NET Business Events feature that led to incoming HTTP web requests not working correctly. (OA-35401)
Reduced overhead of OneAgent CLV/RAP features for .NET applications in a corner case. (OA-36096)
Go
Fixed a call stack reporting issue in the Go CPU profiler that affects Go version 1.21 and later. (OA-35223)
Mainframe
Service calls will now be more balanced due to the randomization of server IDs for mainframe agents. (OA-35883)
Resolved an issue in which, due to exceptions in handling messages from the mainframe, the zRemote was exhausting its pool of parsing buffers. (OA-36745)
Network module
Fixed a oneagentnetwork memory leak. (OA-35817)
Node.js
Fixed an issue that, starting with OneAgent 299, broke Node.js applications using KafkaJS. (OA-36578)
OS module
Log throttling was added to functionality responsible for detecting the relation between DISK and EBS_VOLUME entity. (OA-36638)
Resolved an issue with NFS shares not being properly detected on Linux hosts. (OA-35350)
Fixed an issue where checking the status of container process tracers on a host with many containers took too long, leading to gaps in metrics. (OA-35994)
Fixed an issue on pages using Constructed StyleSheets with WebComponents, where some operations recorded by Session Replay could have wrong timings assigned to them, causing them to be replayed earlier than they should. (SR-5978)
Fixed an issue where callback end time would be greater than action duration. (RUM-6394)
Fixed an issue caused by an incomplete implementation of NavigationTimings on Mobile Safari that caused sessions from different users to be merged. (RUM-22097)
Fixed an issue where the RUM JavaScript agent was not correctly linking resource timings with corresponding XHR calls. (RUM-21918)