With this release, the following are the oldest supported OneAgent versions.
| Support level | Oldest supported version |
|---|---|
| Standard Support | 1.303 |
| Enterprise Success and Support | 1.297 |
For details, see How long are versions supported following rollout?.
Platform | Oneagent
Node.js v10 support will be discontinued with OneAgent version 1.327. Starting with OneAgent version 1.321, automatic injection in Node.js v10 processes is no longer available.
You can still instrument Node.js v10 processes by adding environment variable DT_SUPPORT_DEPRECATED_NODE_VERSIONS when starting the affected process. If the environment variable is available, a warning will be logged and the instrumentation will be performed.
Application Observability
We added Go Application Security support for the breaking change introduced with Go 1.24.5 and 1.23.11.
Definition of the technology support version schema with examples:
Major version 5 is supported
Minor version 5.1 is supported
Patch version 5.1.1 is supported
Version range 5.1 – 5.3 is supported
The minimum required version is 5+
For more information, see New technology support.
For more information, see End-of-support announcements.
Infrastructure Observability | Kubernetes
You can now deploy OneAgent with the Dynatrace Operator in FIPS mode more easily. This simplifies setup for both cloud-native full-stack and application monitoring deployment modes, helping you meet the compliance requirements. For more information, see Install Operator in FIPS mode.
Infrastructure Observability | Java
Java 25 processes are now fully monitored. We now support LTS versions plus the last four Java versions (21, 22, 23, 24).
With OneAgent version 1.321, Java 20 is no longer monitored. If you are running Java 20, you can either update to Java 21+ and monitor your processes with OneAgent version 1.321 or you can keep using Java 20 with OneAgent version 1.319 and earlier.
Infrastructure Observability | Hosts
OneAgent detects the systemd version detection primarily from the pkg-configfile.
Application Observability
The OneAgent .NET code module fully supports RabbitMQ version 7+.
Infrastructure Observability | Hosts
All events generated by Disk Edge are enriched with dt.entity.disk dimensions to easily filter out all events related to the specific disk.
Application Observability
The OneAgent Java code module supports ExtendedTracer and the ExtendedSpanBuilder interface added with OpenTelemetry version 1.42.
Infrastructure Observability | AWS
In AWS Lambda, you can enable OpenTelemetry interoperability for Node.js via DT_OPEN_TELEMETRY_ENABLE_INTEGRATION and dtconfig.json, similarly to Java and .NET. To learn more, see OpenTelemetry interoperability.
Application Observability | Distributed Tracing
We added new AWS Lambda Layers for automatic AWS Lambda Instrumentation (Tracing, Log Correlation). The new support includes AWS SDK, such as SQS, SNS, databases, such as DynamoDB and Redis, EventBridge, and Lambda Triggers.
Application Observability
The OneAgent GraalNative image now creates traces in SpringBoot using the Netty library to handle incoming web requests.
Infrastructure Observability | Hosts
To improve OneAgent OS module stability, the host hardware information is now read from SMBIOS data on the host instead of from WMI calls.
Application Observability
You can explore AWSSDK.Core package traces, providing AWS specific information. We recommend using the OneAgent feature .NET +Http+Client V2 for correct service detection and clean traces.
Platform | Oneagent
The agent/bin/<agent_version>/ directory in the Windows PaaS package has been renamed to agent/bin/current/.
Infrastructure Observability | Hosts
sha256: prefix when a SHA256 hash is detectedThe OneAgent OS module adds a sha256: prefix to the container image ID when a SHA256 hash is detected and the ID string doesn't already contain that prefix.
Platform | OneAgent
The OneAgent Java module supports the Apache Pekko library—a license-free fork of the Akka library. It offers the same feature set for Pekko as it does for Akka, ensuring seamless integration and observability.
The OneAgent feature Java Apache Pekko is enabled by default. To use this library, make sure the following features are enabled as well:
Infrastructure Observability | Hosts
OneAgent uses introspection XML to detect systemd features, instead of hardcoded systemd versions.
Infrastructure Observability | Docker
The OneAgent OS module directly calls the Docker API. Use of the Docker CLI is now considered a fallback path.
Application Observability | Distributed Traces
Dynatrace detects cases in which a JMX attribute is added or removed and refreshes the JMX cache.
Refreshing the JMX cache is seamless and has negligible overhead. To turn it off, set optionDisableJmxAutomaticAttributeRefreshJava to true (optionDisableJmxAutomaticAttributeRefreshJava=true)
Platform | OneAgent
Secrets, such as tenant token and proxy, are no longer visible as *** in logs. Instead, they are hashed with SHA256 to allow simpler verification.
Infrastructure Observability
Multiple ExternalCallAttachments are aggregated in a single entry within a distributed trace.
Platform | Oneagent
The zRemote module now supports RHEL 10.0 x86.
Infrastructure Observability | AWS
Automatic tracing of the AWS SDK S3 client in Java applications (AWS SDK version 2+) is now supported.
Platform | OneAgent
OneAgent native libraries (Code Modules and Infrastructure Agents) are now compiled on Centos 7. Instrumenting applications running in unsupported containers, including Centos 6 or equivalent containers, is no longer available.
Digital Experience | RUM Mobile
Added support for OkHttp version 5.
Digital Experience | RUM Mobile
Added a corruption handler to fix OneAgent crashes triggered by corrupted files.
Digital Experience | RUM Mobile
DTXSpeedUpLifecycleInstrumentation defaults to true, speeding up the OneAgent start.
Digital Experience | RUM Mobile
To improve its usability, the eventContext parameter of the eventModifier function has been changed from an array of various types to an object with named properties.