OneAgent release notes version 1.277
Rollout start: Oct 26, 2023
With this release, the oldest supported OneAgent versions are:
Standard Support
Enterprise Success and Support
1.259
1.253
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.
- .NET 8 (.NET module)
- Azure Cosmos DB 3.18+ (.NET module). OneAgent feature: .NET Azure Cosmos DB
- IBM App Connect Enterprise CICSRequest node (ACE module)
- Jetty HTTP client 12 (Java module)
- Jedis Redi 5 (Java module)
- Go 1.21 (Go module)
- NGINX 1.25.2, 1.25.3 (NGINX module)
- Ubuntu 23.04 (OS module)
End of support
For more information, see End of support announcements.
New features and enhancements
Simplified calculation of CGI ID in Kubernetes and OpenShift
Infrastructure Observability
Calculation of CGI ID in Kubernetes and OpenShift has been simplified, which affects PG ID calculation. Only the Kubernetes cluster ID, namespace, pod name, and container name are used.
With this change, however, if you are using a process naming rule with {ProcessGroup:KubernetesContainerName}
, it may resolve to a double container name. For example, apache-*
could become apache-* apache-2
).
Windows - network disk monitoring enabled
Infrastructure Observability | Hosts
Monitoring of network disks on Windows is enabled.
Note that this can create a security event log notifying that a process token was duplicated, but this is expected behavior and should not be interpreted as a security concern.
Resolved issues
General Availability (Build 1.277.165)
The 1.277 GA release contains 13 resolved issues (including 1 vulnerability resolution).
All modules
- Vulnerability: The libcurl library has been upgraded to version 8.4.0 in response to CVE-2023-38545. (EP-18674)
- Fixed getting Heroku memory limit. Newer Heroku versions claim to use cgroup version 2, but the memory limit is still available in the cgroup version 1 file. The affected Linux kernel version was kernel 5.15.0-1041-aws. (OA-21025)
- Fixed an issue that could cause a deadlock in the host module's process discovery code in full-stack installations on Linux. (OA-20216)
Mainframe
- In a Shared Queues IMS, the path no longer times out if a transaction doesn't produce a response message. This fix also corrects another issue where two paths were produced instead of one when using MSC. (OA-19543)
Node.js
- Fixed an issue in which Node.js failed to detect MySQL database calls in certain cases. (OA-23363)
OS module
- PG ID calculations for non-deep monitorable processes have been fixed to strip numbers (IDs) from Kubernetes container name by default. The same logic is already used for deep-monitored processes. With this fix, we avoid incorrect PG assignments when both deep-monitored and non-deep-monitored processes belong to the same PG. However, this fix forces the recalculation of the affected PG ID (non-deep monitorable processes running in Kubernetes that have numbers in container names). You can opt out of this fix if PG ID recalculation is unacceptable. Please contact support for more information. (HOST-3845)
OneAgent Installer
- SELinux module installation, in case of failure, is now retried in longer intervals, improving OneAgent installer success frequency. (DMX-6192)
OneAgent SDK for C/C++
- Fixed URLs being displayed with appended "?[declared unavailable by agent]". The incoming and outgoing web request tracer's URL was incorrectly displayed depending on certain settings and Dynatrace component version combinations. This agent version changes how URLs without queries are internally transmitted by OneAgent to be compatible with all combinations. (OA-20208)
Java
- The Java code module for z/OS now correctly creates the Remote Call service for CTG Server calls with a high duration. (OA-20628)
- Resolved an issue causing Java business events to not capture the request body when the application read it using `ServletRequest::getReader`. Previously, the OneAgent Java code module only captured request bodies that were read using the `ServletRequest::getInputStream` API. Now, request bodies that are read using `ServletRequest::getReader` are also captured. (OA-19813)
.NET
- Fixed an issue in the OneAgent .NET code module, which captured bizevents twice for a single ASP.NET Core request. (OA-23285)
- Fixed an issue in the .NET GRPC sensor that resulted in incorrect reporting of crashes in the web UI. (OA-23798)
IIB
- The internal state of asynchronous request nodes (such as for Callable, HTTP, SOAP, and REST) was dropped in cases where the response wasn't received within 30s, which produced heavy delays of PurePath distributed traces because they weren't closed and ran into a timeout. This 30s response wait time has been corrected with the timeout defined in the request node property (plus an additional safeguard period of 30s). (OA-23198)
OneAgent for iOS
General Availability (Build version_8.277.1)
The version_8.277 GA release contains 1 resolved issue.
OneAgent for iOS
- Improved compatibility for projects with user script sandboxing. (RUM-13115)
OneAgent for JavaScript resolved issues
General Availability (Build 1.277.163)
The 1.277 GA release contains 1 resolved issue.
JavaScript
- Fixed a bug in which created XHR actions never closed within the Angular module due to missing newer Angular router events Scroll and NavigationSkipped. (RUM-13297)