What's new in Dynatrace OneAgent version 1.327

  • Release notes
  • 6-min read
  • Rollout start on Nov 18, 2025

This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.327. It contains:

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

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

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

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.

Feature updates

Application Observability

Add additional support for AWSSDK.DynamoDBv2

A specialized sensor for AWSSDK.DynamoDBv2 was implemented for monitoring database calls.The feature can be enabled via the feature controller .NET AWS DynamoDB.

Application Observability | Distributed Tracing

Support for Go 1.25.3 and 1.24.9

Added Go 1.24.9 and 1.25.3 support.

Application Observability | Distributed Tracing

Support for Go 1.24.8 and 1.25.2

Added Go 1.24.8 and 1.25.2 support.

Application Observability | Distributed Tracing

Distributed tracing support for AWSSDK.Lambda

Added tracing support for Lambda invocations via AWSSDK.Lambda.

Application Observability | Distributed Tracing

ARM support for OneAgent Go code module

Added support for Go code module stripped ARM64 binary monitoring.

Application Observability | Distributed Tracing

Generic AWS SDK v2 support for outbound REST API calls

Added generic tracing support of all Go AWS service calls made via github.com/aws/aws-sdk-go-v2.

Application Observability | Distributed Tracing

Add support for AWSSDK.SimpleNotificationService (SNS)

A sensor for the AWSSDK.SimpleNotificationService package was implemented, which allows tracing of SNS messages. The feature can be enabled via the feature controller .NET AWS SNS Producer.

Digital Experience | RUM Web

RUM server timings on Netty support

Improved linking of user actions to distributed traces by utilizing Server-Timing HTTP header for the Netty RUM feature Netty Real User Monitoring (RUM) to distributed trace correlation.

Platform | OneAgent

Technology Support - z/OS

Added support for z/OS 3.2.

Platform | OneAgent

Support for Rocky Linux 9.6 x86

The zRemote now supports Rocky Linux 9.6 x86.

Platform | OneAgent

Support for RHEL 9.6 s390

The zRemote has been successfully tested with RHEL 9.6 s390.

Platform | OneAgent

Optimize CPU consumption of z/OS Java code module

Added improvements on the handling of JDBC sensors to optimize CPU consumption.

Platform | OneAgent

Support for Rocky Linux 10.0 x86

The zRemote supports Rocky Linux 10.0 x86.

Platform | OneAgent

Support for Oracle Linux 10.0 x86

The zRemote supports Oracle Linux 10.0 x86.

Breaking changes

Platform | OneAgent

Downgrade of RUM v2 feature from opt-in to DevOps-only

The Java Real User Monitoring v2 feature (key: JAVA_UEM_INSTRUMENTATION) has been renamed to Java Real User Monitoring (RUM) Troubleshooting Mode and downgraded from opt-in to DevOps-only. The feature is now available only to DevOps teams for troubleshooting purposes.

Fixes and maintenance

Resolved issues in this release

  • Fixed an issue with the Threading Sensor instrumenting an endless loop in KafkaMessageListenerContainer$ListenerConsumer. (OA-54736)
  • Fixed a memory leak in OneAgent's OTEL span sensor caused by thread-local variable retention, which led to excessive memory usage. The issue was resolved by optimizing memory management to ensure stable performance. (OA-54725)
  • Fixed an issue that led to missing data in ADO tracing. (OA-54606)
  • On Windows, boost::icontains makes use of a lock that takes a consistent amount of time. The replacement function does not use any lock. (OA-54564)
  • Fixed log streaming issues after a CICS Agent would unINIT, and then reINIT. (OA-54319)
  • Removed deprecated handling on OneAgent where HTTP requests would be identified as JavaScript Agent Requests based on the jsAgentFilename or jsAgentFilenameDebug from the application UEM setting. (OA-54219)
  • Fixed an issue where CICS Services were missing due to mishandling of certain types of paths, in particular paths that reused MQ msg ID and correlation IDs. (OA-53529)
  • Fixed a possible crash caused by the OneAgent .NET Code Module in a corner case related to duplicate namespace and class names. (OA-53327)
  • Memory usage was reduced for instances when the agent installer is downloaded from a tenant. (OA-52651)
  • Fixed an issue with Apache/NGINX/IIS that sometimes led to response body sizes not matching the content-length header, when bizevents are enabled and some compression is used (gzip, deflate, br). (OA-52314)