This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.333. It contains:
Application Observability | Log Analytics
The Dynatrace Log module now provides environment-wide self-monitoring features. You get:
For details, see Implement Log module self-monitoring.
To use self-monitoring features, you need:
New features include:

For assistance during any phase of the release, open a support ticket or consult the troubleshooting guide linked in the dashboard.
The functionality requires Log Management and Analytics powered by Grail, with support for OneAgent and Dynatrace Operator deployment modes enabled by the schema ID builtin:logmonitoring.log-sfm-settings. It is disabled by default and can be manually activated via the Settings API.
With this release, the following are the oldest supported OneAgent versions.
| Support level | Oldest supported version |
|---|---|
1.315 | |
1.309 |
For details, see How long are versions supported following rollout?.
Application Observability | Distributed Tracing
We added new AWS Lambda layers for automatic Go instrumentation (tracing, log correlation). The new support includes the generic AWS SDK and SNS.
Application Observability | Distributed Tracing
OneAgent now supports Spring Boot 4.0 and Spring Framework 7.0 versions.
Application Observability | Distributed Tracing
We have introduced automatic suppression of OpenTelemetry spans based on the OpenTelemetry instrumentation library name. If a OneAgent sensor is available that instruments the same library as the OpenTelemetry instrumentation, OpenTelemetry spans are automatically suppressed to avoid double tracing. For a list of OpenTelemetry instrumentation libraries affected by this behavior, see Prevention of span duplication in Node.js.
Application Observability | Log Analytics
We've introduced the Detection of a plain IIS configuration feature that enables OneAgent to assign logs to the appropriate IIS application pools unambiguously.
When the feature is activated, OneAgent verifies whether the IIS setup is complex or plain. A plain configuration means that a single application pool is assigned to a single site, and there is no central log shared across the entire IIS instance.
The plain configuration assigns logs to the processes of individual pools instead of assigning all logs to a single IIS process.
To activate the Detection of a plain IIS configuration feature:
Digital Experience | RUM Web
You can now call dtrum.enableAutomaticPageDetection to restore automatic page detection after using manual page detection.
Infrastructure Observability | Azure
We have added a new integration option to monitor Azure App Service on Linux using the sidecar pattern. This provides a simplified integration with code-only and custom container deployments.
Platform
We have added support for Fedora 43.
Platform
We added support for Debian 13, where /etc/sysctl.conf is no longer used and has been replaced with /usr/lib/sysctl.d/50-default.conf (from the linux-sysctl-defaults package) and local snippets in /etc/sysctl.d/*.conf. Other distributions may follow this pattern. For more details, see Debian 13 release notes, section 5.1.15.
Platform | OneAgent
Tracing support for Redisson is now available, including support for tracing queries and batched queries. To enable this, turn on Java Redisson Redis client. This instrumentation can optionally distinguish between batch operations (turned off by default).
Platform | OneAgent
ES6 modules are now supported in Node.js.
Platform | OneAgent
Tracing support is now available for Vert.x WebClient and HttpClient for versions 3.6+, 4.X, and 5.X.
Platform | OneAgent
We have added the Python 3.14 distribution to the OneAgent deployment for extensions.
Infrastructure Observability | Extensions
Python extensions can now be run with Python 3.14. To enable this, rebuild the extension with the newest Python SDK.
log level or timestamp attributes in JSON documents. (OA-60996)product_serial and sys_vendor) for OneAgent on Linux, ensuring accurate and consistent system metadata reporting. Previously, it used chassis metadata for system.serial and system.vendor, leading to inaccurate system identification. (OA-60568)aws.account.it and aws.region) were missing on spans. (OA-59686)timezone parsing issue when configured for log ingestion. (OA-59582)@RestController methods with @PreAuthorize or/and @PostAuthorize annotations for spring-boot-starter-securityversions 2.5+. (OA-59449)MINTv2 metrics sent from OneAgent to the December 2025 MINTv2 specification update. That update relaxed the requirements for the first character of the dimensions key from ('a'..'z' | 'A'..'Z' | '') to the regex [\x21-\x7E]. Characters previously converted to _ will now remain unchanged. (OA-59395)classicFullStack. (OA-57123)