OneAgent release notes version 1.301

Pre-release information

This is an ongoing summary of changes in this planned release. Check back here at GA for the final version.

Rollout start: Oct 8, 2024 (planned)

For environments with Extensions 1.0, rollout starts after Oct 31, 2024. See End of life announcement.

With this release, the following are the oldest supported OneAgent versions.

Support level
Oldest supported version

For details, see How long are versions supported following rollout?.

Breaking changes

Extensions 1.0 framework end of life

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.

For more information, see General guidance and how to migrate.

Technology support

Definition of the technology support version schema with examples:

  • Major version 5 is supported

    • Major version 5 is supported, including all of its minor versions like 5.1 and 5.2
    • Other major versions are not supported like 6 and 7
  • Minor version 5.1 is supported

    • Minor version 5.1 is supported, including all of its patch versions like 5.1.1 and 5.1.2
    • Other minor versions are not supported like 5.2 and 5.3
  • Patch version 5.1.1 is supported

    • Patch version 5.1.1 is supported
    • Other patch versions are not supported like 5.1.2 and 5.1.3
  • Version range 5.1 – 5.3 is supported

    • Minor versions 5.1, 5.2, and 5.3 are supported, including all of their patch versions like 5.1.1, 5.2.1, and 5.3.1
    • Other minor versions are not supported like 5.0 and 5.4
  • The minimum required version is 5+

    • All major, minor, and patch versions starting from version 5 are supported, like 5, 5.1, 5.1.1, and 6

New technology support

For more information, see New technology support.

End of support

For more information, see End of support announcements.

New features and enhancements

Host-level resource attributes

Infrastructure Observability | Hosts

We have added k8s.node.name to the host-level resource attributes.

Host availability events on host shutdown and reboot

Infrastructure Observability | Hosts

We have enabled functionality to send host availability events on host shutdown and after host reboots, including dirty reboot detection.

Resolved issues

General Availability (Build 1.301.45)

The 1.301 GA release contains 15 resolved issues.

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)

.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)

General

  • 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)

Java

  • Improved the Tibco 5 introspection code to resolve an issue causing a 10-minute timeout with some traces because they were not finished correctly by the sensor. This fix addresses a problem the sensor had with Tibco workflows not handling end events properly. (OA-34706)

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)

OneAgent for Android

General Availability (Build 8.301.1)

The 8.301 GA release doesn't contain any user-facing resolved issues.

OneAgent for iOS

General Availability (Build 8.301.0)

The 8.301 GA release doesn't contain any user-facing resolved issues.

OneAgent for JavaScript

General Availability (Build 1.301.4)

The 1.301 GA release contains 3 resolved issues.

JavaScript

  • Fixed an issue where callback end time would be greater than action duration. (RUM-6394)
  • 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 caused by an incomplete implementation of NavigationTimings on Mobile Safari that caused sessions from different users to be merged. (RUM-22097)