What's new in Dynatrace OneAgent version 1.323

  • Release notes
  • 6-min read
  • Rollout start on Sep 23, 2025

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

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

Support levelOldest supported version
Standard Support1.305
Enterprise Success and Support1.299

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

RedHat FIPS Go 1.23.9 and 1.24.4 support

We added support for FIPS with the Red Hat Go Toolset v1.23.9 and v1.24.4.

Application Observability | Distributed Tracing

New automatic instrumentation for AWS Lambda in Python

We added new AWS Lambda Layers for automatic AWS Lambda Instrumentation in Python (Tracing, Log Correlation). The new support includes AWS SDKs such as SQS and SNS, databases such as DynamoDB and Redis, EventBridge, and Lambda Triggers.

Application Observability | Distributed Tracing

Removed ASP.NET Sensor V1

We removed the deprecated version of ASP.Net Sensor v1 and made Sensor v2 the new default version. If your environment uses ASP.Net Sensor v1, it's automatically switched to Sensor v2, which offers the same feature set with improved support for async web requests and more accurate timings.

Application Security

Improve detection of SSRF vulnerabilities and attacks on Java

Improved OkHttp support for the OneAgent feature Java SSRF code-level vulnerability and attack evaluation.

Application Security | Vulnerabilities

Improved accuracy of code location detection with Java Azure SDK

Improved accuracy of code location detection with the Java Azure SDK. This change only applies to users of the OneAgent opt-in feature Java SSRF code-level vulnerability and attack evaluation. Existing code-level vulnerabilities related to these libraries may change their security vulnerability ID.

Digital Experience | RUM Mobile

Support for Gradle 9.0

We now support Gradle 9.0.

Digital Experience | RUM Mobile

Support for Android Gradle Plugin 8.12

We now support Android Gradle Plugin 8.12.

Digital Experience | RUM Mobile

Support for Jetpack Compose 1.9.0

We now support Jetpack Compose 1.9.0.

Infrastructure Observability | AWS

Automatic AWS SDK Kinesis support for Java

We now support automatic tracing for the AWS SDK Kinesis client in Java applications (AWS SDK version 2.x).

Infrastructure Observability | Hosts

Netty support for business events

We now support Business Events for incoming Netty web requests.

Infrastructure Observability | Hosts

Support overlay filesystem

OneAgent now supports OverlayFS. Only space statistics are supported.

Platform

Changed base image of OneAgent Cloud Native container image

We changed the base image from GCT Distroless to Red Hat UBI9 Micro. The change applies to the OneAgent Cloud Native container image, which is the image located in the following registries:

  • Docker Hub: dynatrace/dynatrace-oneagent
  • AWS ECR: dynatrace/dynatrace-oneagent

Platform

Changed base image of OneAgent classic and Cloud Native container image

We changed the base image from Red Hat UBI9 Minimal to Red Hat UBI9 Micro. This change should result in reduced security vulnerability issues as UBI9 Micro contains fewer packages. The change applies to the OneAgent classic container image, which is the image located in the following registries:

  • Tenant registry: All images (starting from version 1.323)
  • Docker Hub: dynatrace/oneagent (starting from version 1.105.1000)
  • Red Hat Container Catalog: dynatrace/oneagent (starting from version 1.105.1000)

We also changed the base image from GCT Distroless to Red Hat UBI9 Micro. The change applies to the OneAgent Cloud Native container image, which is the image located in the following registries:

  • Docker Hub: dynatrace/dynatrace-oneagent
  • AWS ECR: dynatrace/dynatrace-oneagent

This version of the image is rolled out in a controlled way, because it is a fundamental change to the image. Consequently, the rollout will take longer than usual. We expect the version to be available around October 14th.

Platform | OneAgent

Optimized nodes for Apache Http sync client 4+ and 5+

An HttpRequestExecutor#execute method node and sync link node for each physical request are no longer created by default.

Platform | OneAgent

Go agent ARM support

We now support ARM64 in the Go code module.

Breaking changes

Application Observability | Log Analytics

Binary status detection updated for log sources

Starting from version 1.323, OneAgent detects the binary status of log sources differently. OneAgent now individually checks each file assigned to a log source for binary content. If any file contains binary content, OneAgent marks the entire log source as binary. Additionally, the binary status is permanently assigned to each file.

This change may affect the scope of the transmitted data.

Resolved issues

  • Fixed the issue where host metrics appeared under an alternate host name instead of the expected host identifier. (OA-52730)
  • We fixed an issue in which sensitive information, such as tenant tokens, API tokens, and proxy credentials, was not properly obfuscated in the installer log output for systems using mawk. (OA-53044)
  • Fixed detection of startup class for SpringBoot in versions 3.2+. OneAgent may have reported different startup class names for SpringBoot in versions 3.2+. (OA-51885)
  • We have improved the detection of software components in exploded JAR files. (OA-49492)
  • If the Java code module is deactivated, it will no longer handle configuration updates for extensions or install new ones. (OA-51633)
  • OneAgent Node.js is now injected using --require option. This solves an existing issue in Next.js 15+ for the commands next dev or next build usually called from npm run dev or npm run build in the apps created via npx create-next-app. (OA-52416)
  • CRI-O containers with a non-default container storage path are now detected. (OA-54020)

    OneAgent for Android

      OneAgent for iOS

        OneAgent for JavaScript