OneAgent SDK for Android upgraded to Kotlin 1.9.10
Breaking change
The OneAgent SDK for Android has been upgraded to Kotlin 1.9.10. For official Kotlin documentation, see Kotlin release details.
Apps using Kotlin 1.8 should be still compatible.
Earlier versions may need adjustments to compile. In that case, refer to the official Kotlin documentation. Most issues should be resolved by ensuring you are up to date with Gradle and the Android Gradle plugin versions as explained in the Kotlin documentation.
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
Fixed possible duplicate reporting of IP addresses for database services (resulting in service detection on the cluster side creating a duplicate database service) when OneAgent's hostname resolver periodically updates DNS records. (OA-25100)
Fixed an incompatibility with the musl-libc `gcompat` library that could lead to a crash of any applications (no matter if linked against musl or glibc) that were executed on musl-libc with its `gcompat` wrapper library when OneAgent was loaded. (OA-26645)
The Kubernetes pod name can be determined from the hostname. On Windows, the fully qualified domain name was used instead of the host name, which could lead to incorrect pod name recognition. With this fix, the physical machine name is now used, which is the expected behavior. (OA-24453)
When resolving the DNS name fails on first try to connect to an SNMP device, datasource will retry the connection in the next interval. (EXT-8614)
Fixed OneAgent deployment on RKE2 instances (installation failed due to oneagenthelper process termination caused by insufficient permissions to access the containerd meta.db file). (OA-25919)
Java
The HTTP response body of business events is now properly captured even if GZIP compression happens outside the Servlet filter chain. (OA-24574)
Fixed a memory leak that occurred when Grail metrics were disabled. (OA-26888)
.NET
The request body is no longer stripped away when a Business Event rule to capture the request body is set. (OA-25428)
IIB
Dynatrace OneAgent code module for IBM ESB: Resolved issue that possibly altered customer message headers used for Dynatrace tagging. (OA-25465)
Mainframe
Distributed traces from CICS and IMS are now correctly marked as flawed if the node limit was exceeded. (OA-24964)
OS module
Fixed an issue in which a Spring Boot process was occasionally assigned to an invalid process entity. (HOST-4726)
Containers running in a private user namespace are now detected. (HOST-4485)
Fixed grouping and detecting Spring Boot version 3.2. (HOST-4912)
Java processes are now properly reported in cases when JRE is inaccessible from the OS module. (HOST-5252)
OneAgent Installer
Modified SELinux policies to allow `ioctl` syscall to access Dynatrace enrichment metadata files. (DMX-6756)
OpenTracing module
Starting with OneAgent 281, the OneAgent Envoy code module is no longer injected into (and there is no deep monitoring of) Envoy version 1.29+. Previously, Envoy could abort startup with an error in Envoy versions that no longer support certain features required by OneAgent. (OA-24962)
Update 137 (Build 1.281.137)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.281 release.
General
Fixed an incompatibility with the musl-libc `gcompat` library that could lead to a crash of any applications (no matter if linked against musl or glibc) that were executed on musl-libc with its `gcompat` wrapper library when OneAgent was loaded. (OA-26645)
Update 161 (Build 1.281.161)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.281 release.