OneAgent release notes version 1.321

  • Release notes
  • 4-min read
  • Rollout start on Sep 10, 2025

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

Support levelOldest supported version
Standard Support1.303
Enterprise Success and Support1.297

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

Breaking changes

Platform | Oneagent

OneAgent no longer injects Node.js v10 processes by default

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

Support for Go 1.24.5 and 1.23.11 breaking changes

We added Go Application Security support for the breaking change introduced with Go 1.24.5 and 1.23.11.

Technology support

Technology support version schema

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

For more information, see New technology support.

End of support

For more information, see End-of-support announcements.

New features and enhancements

Infrastructure Observability | Kubernetes

Streamlined FIPS mode deployment on 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

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

Improved systemd version detection

OneAgent detects the systemd version detection primarily from the pkg-configfile.

Application Observability

Support for RabbitMQ 7+

The OneAgent .NET code module fully supports RabbitMQ version 7+.

Infrastructure Observability | Hosts

Disk Edge events enriched with disk entity dimensions

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

Support for OTel incubator API

The OneAgent Java code module supports ExtendedTracer and the ExtendedSpanBuilder interface added with OpenTelemetry version 1.42.

Infrastructure Observability | AWS

Enable OpenTelemetry interoperability for Node.js

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

Automatic Instrumentation for AWS Lambda in Java and Node.js

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

GraalNative image traces in SpringBoot via Netty

The OneAgent GraalNative image now creates traces in SpringBoot using the Netty library to handle incoming web requests.

Infrastructure Observability | Hosts

Improved OneAgent OS module stability

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

New tracing support for the AWSSDK.Core package (.NET)

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

Renamed directory for Windows PaaS package

The agent/bin/<agent_version>/ directory in the Windows PaaS package has been renamed to agent/bin/current/.

Infrastructure Observability | Hosts

Container image IDs sha256: prefix when a SHA256 hash is detected

The 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

Support for Apache Pekko

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:

  • Java/Scala Apache Pekko HTTP Server
  • Java/Scala Apache Pekko HTTP Client
  • Java/Scala Apache Pekko Remoting

Infrastructure Observability | Hosts

Detection of systemd features based on introspection XML

OneAgent uses introspection XML to detect systemd features, instead of hardcoded systemd versions.

Infrastructure Observability | Docker

Enable use of Docker API

The OneAgent OS module directly calls the Docker API. Use of the Docker CLI is now considered a fallback path.

Application Observability | Distributed Traces

Implicit reloading of MBean attribute cache for JMX

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

Hashing secrets

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

Enabled ExternalCallAttachment aggregation

Multiple ExternalCallAttachments are aggregated in a single entry within a distributed trace.

Platform | Oneagent

RHEL 10.0 supported by zRemote

The zRemote module now supports RHEL 10.0 x86.

Infrastructure Observability | AWS

Automatic AWS SDK S3 support for Java

Automatic tracing of the AWS SDK S3 client in Java applications (AWS SDK version 2+) is now supported.

Platform | OneAgent

OneAgent is now built with Centos 7

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.

Resolved issues

General Availability (Build 1.321.51)

The 1.321 GA release contains 20 resolved issues.

ComponentResolved issues
OS module4
Go1
AI causation engine1
Extensions framework2
General3
Live Debugger1
Mainframe4
Network module1
.NET1
NGINX1
Python1

OS module

  • OS Agent no longer crashes upon exit when GPFS mounts are detected. (OA-51639)
  • Changed OneAgent port reporting for Apache Tomcat processes from configured ports only to all listening ports. (OA-50527)
  • Improved the parsing of processes’ environment variables when the output is malformed. (OA-49922)
  • Fixed an issue that prevented a version from being stripped from the container image name for processes of non-injectable technologies running on Docker or Podman. By ignoring the variable image version, existing process groups of the affected processes become more stable; however, they might change. (OA-50478)

Go

  • Fixed a potential crash with applications that link Go code built with buildmode `c-shared`. (OA-49227)

AI causation engine

  • Fixed incorrect trace counting that caused unrealistically high values for the `dt.sfm.oneagent.code_module.traces.processed` metric. (OA-50565)

Extensions framework

  • Fixed improper `dt.metrics.source` enrichment for metrics sent from Extensions, changing the value from invalid {{dynatrace_osagent}} to the name of the extension. (DAQ-11818)
  • `dsruntime` directories are no longer deleted when the extension configuration is changed. (DAQ-10263)

General

  • Fixed the uptime calculation that was leading to zero or negative values. (OA-50944)
  • Introduced new OneAgent feature `Align CloudFoundry App-Only with Full-Stack ID logic` to align Cloud Foundry App-Only logic with the approach used in Full-Stack deployments. When turned on, it enables an alternative method for calculating the Cloud Foundry Application Instance ID in app-only mode. The feature is automatically turned on for new environments and remains off for existing tenants to avoid breaking services. (OA-49023)
  • Added a proper translation for the `AgentIp` OID value to `String` in the SNMP TRAP datasource to avoid incorrect type casting during trap processing. (DAQ-11837)

Live Debugger

  • Reduced Live Debugger memory overhead when some auto-generated classes are used. (OA-52000)

Mainframe

  • Changed value format for null IMS transaction IDs, from eight nulls to a standard empty string. (OA-52205)
  • Fixed an issue that caused the z/OS module to translate backslash (`\`), left bracket (`[`), and right bracket (`]`) incorrectly during processing of log streams. (OA-51057)
  • Fixed IMS-dependent regions not initializing after a zRemote restart. Until the ICTL inits again, the IAPP init is blocked, and the zRemote module ignores IAPP data. (OA-51840)
  • When IMS grouping is turned off, the process group ID of an IMS-dependent region no longer changes from prior versions. (OA-52099)

Network module

  • Added a warning log when the Npcap version is not supported. (OA-50148)

.NET

  • Fixed potential false-positives shown by the Code Level Vulnerability and Attack detection features when using .NET version 8+. (OA-50036)

NGINX

  • Resolved an issue where, under very specific conditions, NGINX could return an empty response when Real User Monitoring (RUM) was enabled and the server was configured with both `ssi` (Server Side Includes) and `proxy_cache`. (OA-49494)

Python

  • Fixed tracing of messages from EventBridge to an SQS queue that caused trace data to indicate the EventBridge was not picked up by the SQS queue, even when the message was processed. (OA-52090)

OneAgent for Android

General Availability (Build 8.321.1)

The 8.321 GA release contains 1 resolved issue.

Android

  • Fixed an issue that impacted crash reporting when the OneAgent crash reporting state was changed while a crash occurred. (DEM-11967)

Digital Experience | RUM Mobile

New OkHttp release

Added support for OkHttp version 5.

Digital Experience | RUM Mobile

Corrupted files handling

Added a corruption handler to fix OneAgent crashes triggered by corrupted files.

OneAgent for iOS

General Availability (Build 8.321.1)

The 8.321 GA release contains 1 resolved issue.

OneAgent for iOS

  • Fixed an issue that caused validation with Apple to fail when using OneAgent static framework. (DEM-13839)

Digital Experience | RUM Mobile

DTXSpeedUpLifecycleInstrumentation defaults to true

DTXSpeedUpLifecycleInstrumentation defaults to true, speeding up the OneAgent start.

OneAgent for JavaScript

General Availability (Build 1.321.3)

The 1.321 GA release contains 2 resolved issues.

JavaScript

  • Fixed an issue that led to the incorrect reporting of `Script Errors`. (DEM-13847)
  • Fixed an issue that caused duplicate waterfall entries on pages with a high number of resources when the native PerformanceObserver was not available. (DEM-11465)

Digital Experience | RUM Mobile

Changed eventContext parameter type

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.