Try it free

What's new in Dynatrace OneAgent 1.347

  • Release notes
  • 9-min read
  • Rollout start on Sep 30, 2026

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

  • Feature updates: 20
  • Breaking changes: 3
  • Fixes and maintenance: 47 (1 vulnerability)

Oldest supported versions

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

Support levelOldest supported version

Standard Support

1.329

Enterprise Success and Support

1.323

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

Feature updates

Application Observability

AWS Lambda support for Spring Cloud Functions

Added AWS Lambda Handler support for Spring Cloud Functions.

Application Observability | Distributed Tracing

Azure SDK Blob Storage support for Java

We now support automatic tracing of the Azure SDK Blob Storage Clients in Java applications.

Application Observability | Distributed Tracing

OpenFeature monitoring in Python

Added reporting OpenFeature flag monitoring for Python.

Application Observability | Distributed Tracing

Microsoft Foundry tracing in Python Agent

Added new Microsoft Foundry tracing in Python.

Application Observability | Distributed Tracing

Azure Function for Python on Premium Plan for Linux

Extended instrumentation for Azure Function (tracing, log correlation) for Premium Plan for Linux for Python.

Application Observability | Distributed Tracing

Implemented tracing support for Azure CosmosDB client for Node.js

Node.js applications that access Azure CosmosDB via @azure/cosmos package are now traced.

Application Observability | Distributed Tracing

Spring Cloud Stream Kafka Binder (Consumer side, single mode)

OneAgent now has tracing support for Spring Cloud Stream Kafka Binder (Consumer side) in single mode.

Application Observability | Distributed Tracing

Server-Timing metrics in one header

Changed Server-Timing header emission to consolidate all metrics into a single header instead of two separate headers. This resolves compatibility issues with applications that don't handle repeated Server-Timing headers correctly.

Application Observability | Distributed Tracing

Spring Cloud Stream Kafka Binder (Consumer side, batch mode)

OneAgent now has tracing support for Spring Cloud Stream Kafka Binder (Consumer side) in batch mode.

Application Observability | Log Analytics

Updated default set of JSON severity keys

We have added levelname, lvl, log.level, and log_level as default JSON severity keys.

Digital Experience | RUM Web

Improved Traffic Control behavior in RUM

Fixed an issue where RUM JavaScript ignored traffic control settings and sent events to Grail when data collection should have been suppressed. This issue did not impact Real User Monitoring Classic (RUM Classic) and billing.

Digital Experience | RUM Web

Source for user actions

A hard_navigation user action now shows what caused the navigation. When a user clicks a link on a page, the hard_navigation user action on the next page includes the interaction that triggered it, the clicked element, and the view the click originated from. If a user action was active instead of a direct click, that user action is reported as the source along with the interaction that triggered it. Navigation timing data also now shows the view the user navigated from.

Digital Experience | RUM Web

New triggers for user actions

RUM JavaScript now creates user actions for drop events, input changes, and Enter keypresses, expanding user action generation beyond click interactions.

Infrastructure Observability | Hosts

Java 27 processes are fully monitored

Java 27 processes are now fully monitored.

  • We now support LTS versions plus the last four Java versions (24, 25, 26 and 27).
  • Starting from OneAgent version 1.347, Java 23 is no longer monitored. If you are running Java 23, you can either update to Java 24+ and monitor your processes with OneAgent version 1.347, or you can keep using Java 23 with OneAgent version 1.345 and earlier.

Infrastructure Observability | Hosts

Support for CentOS Stream 10

Added support for CentOS Stream 10 for OneAgent.

Infrastructure Observability | Hosts

Rust and Tokio technology detection

Implemented Rust and Tokio process technology detection.

Infrastructure Observability | Hosts

Improved detection of short-lived processes

We have improved the reliability and accuracy of short-lived process detection on Linux distributions with Kernel 5.8+. Now processes are detected properly across multiple CPUs, and this detection also works on the ARM64 architecture.

Platform | OneAgent

Non-root user for OneAgent container in classic full stack mode

Dynatrace Operator in classic full stack mode now runs a OneAgent container with a non-root user.

Platform | OneAgent

Support for monitoring of Spring Cloud Stream Kafka Binder consumers

OneAgent now traces Spring Cloud Stream Kafka Binder consumers in both single and batch consumption modes.

  • Single mode—java.util.function.Consumer with standard (non-batch) message consumption is now traced automatically.
  • Batch mode—java.util.function.Consumer with spring.cloud.stream.bindings.<name>.consumer.batch-mode: true is now traced automatically.

Platform | OneAgent

SFM event to reflect CPU quota exhaustion

The Log module’s CPU usage is now controlled by OS Agent and Watchdog. Once its assigned quota is reached, the Log module is throttled (CPU usage is limited) and a new SFM event resource.cpu_quota_exhausted is sent.

Breaking changes

Digital Experience | RUM Web

Improved user actions

Updated how navigations and user actions interact for more natural representation. User actions are always triggered by a user via an interaction, and if (soft) navigations occur, they are now part of the same user action, even when multiple navigations happen in quick succession. The set of interactions that can trigger user actions has also been extended to include drop, change, and Enter keypresses.

Infrastructure Observability | Hosts

Composefs filesystem is no longer monitored

The composefs filesystem is no longer monitored as it is an overlay subtype which is read-only and always shows 100% usage thus triggering false positive alerts.

Uncategorized

Switch to Cosign for container image signature verification

Starting from December 1, 2026, Dynatrace will only support Cosign for container image signature verification. Docker Content Trust will no longer be supported after this date.

Who is affected?

This change affects customers who:

  • Pull the dynatrace/oneagent container image from Docker Hub.
  • Verify container image signatures as part of their deployment, compliance, or security processes.

Required action

If you currently verify Dynatrace container image signatures via Docker Content Trust, update your verification process to use Cosign before December 01, 2026. For details, see Verify image signatures using Cosign.

Fixes and maintenance

General Availability (1.347.0.20260820-154158)

  • Fixed an issue where OneAgent log monitoring could terminate repeatedly when a monitored pod reported Kubernetes namespace annotations that could not be parsed. (OA-73972)
  • Fixed an issue where the psycopg2 sensor caused a TypeError when a proxied Cursor or Connection object was passed to native psycopg2 functions such as quote_ident. (OA-73403)
  • Fixed Garden container detection and injection in cgroupv2 environments. (OA-73220)
  • Fixed an issue with IMS Configurations that caused excessive log messages. (OA-73175)
  • Fixed an issue where OneAgent Node.js injection incorrectly handled the errorCodes and LogController exports from fastify. (OA-73113)
  • Added z/OS Java module support for Java 25 LTS. If you run z/OS Java against Java Development Kit version 24+, you should run Java processes with the --sun-misc-unsafe-memory-access=allow Java Virtual Machine arguments to disable deprecation logging messages at startup. (OA-73076)
  • Fixed an issue where CICS and IMS configurations were not grouped for similar configurations, so the z/OS Data Collection (zDC) subsystem exhausted its configuration slots. (OA-72954)
  • Fixed an issue where server.address was not resolved correctly when using MongoDB 3.x or 4.x–5.5 with the useUnifiedTopology option (as used by the Mongoose connector), causing the MongoDB service to appear without its associated database host details. (OA-72934)
  • Fixed a crash in Python confluent_kafka tracing where calling store_offsets() for manual offset management raised a TypeError. (OA-72747)
  • OS Service monitoring now correctly reports the inactive state when a service is stopped and unloaded by systems on monitored Linux hosts. The service is reported as inactive for the duration it remains stopped, and the availability alert is thrown. (OA-72737)
  • Fixed an issue where OneAgent Python tracing failed to instrument AWS Lambda handler functions wrapped with a decorator that adds extra parameters beyond the standard (event, context) signature, even when the decorator used functools.wraps. As a result, no service entity was created for the affected Lambda functions. (OA-72629)
  • Fixed an issue where OneAgent Python injection unconditionally removed sitecustomize from sys.modules but only restored it when the injected sitedir was the first entry in sys.path. (OA-72627)
  • Changed the Java Virtual Machine free memory description so it’s more accurate in Fullstack deployments. (OA-72620)
  • Fixed an issue where DB2 metrics were not reported on z/OS despite DB2 process groups being created and registered correctly. (OA-72481)
  • Fixed a bug where OneAgent would capture the wrong server name for WebSphere Liberty if overridden. (OA-72298)
  • Fixed an issue in Python kafka tracing where iterating Kafka poll results more than once caused the second iteration to return a raw generator object instead of the actual message lists, resulting in silent data loss for applications that process poll results in multiple passes. (OA-72000)
  • Fixed a configuration issue where CICS and IMS configuration did not flow correctly to the mainframe from the tenant. (OA-71898)
  • Fixed a class-name conflict that could prevent applications from loading when Code-Level Vulnerability Analytics or Runtime Application Protection was activated, affecting frameworks that map Java classes by simple name, such as FICO Blaze Advisor. (OA-71825)
  • Fixed an issue where the OneAgent Java module created OpenTelemetry spans that violated the reflexivity requirement of the Object::equals method. (OA-71755)
  • Corrected the metrics on the Azure Service Bus consumer side to avoid false positive alerts. (OA-71647)
  • Fixed a performance overhead in Go applications on Linux x86 that use the CGO framework to invoke Go code from C at high frequency. This only affects calls made on threads created in C, not in Go. (OA-71585)
  • Fixed an issue where OneAgent bootstrapper failed to determine the volume host path in cloudNativeFullStack deployments on SUSE Linux, which uses btrfs with subvolumes by default. (OA-71511)
  • Fixed BOSH container detection for BOSH Process Manager version 1.4.33+. (OA-71339)
  • Changed the CPU Saturationevent description from CPU idle threshold below {}% to CPU usage above {}%. (OA-71303)
  • Fixed a potential crash in Go applications when Go technology monitoring was turned off and then turned on again, caused by an out-of-bounds access in the AmbientSampling component. (OA-71301)
  • Fixed a crash in zRemote caused by unsynchronized access to IMS Address Space. (OA-71235)
  • Fixed crashes of Node.js worker threads when the process was started with arguments that are not valid for worker threads. (OA-71055)
  • Fixed an issue where CICS transaction tracing stopped reporting after a zRemote restart, caused by a configuration handling error in zRemote that left CICS regions in an untraced state. (OA-71003)
  • Improved log stream robustness by adding implicit registration as a fallback when a stream is not explicitly registered, reducing the risk of log stream loss. (OA-70987)
  • Improved Java classloader performance in OneAgent by eliminating unnecessary class-loading attempts triggered on every outgoing HTTP call when using DynamicProxy objects. This affected applications using the JDK 11 HTTP client, Quarkus, Vert.x, WebFlux, and Akka HTTP, where repeated ClassNotFoundException exceptions were causing measurable CPU and memory overhead. (OA-70921)
  • Fixed incorrect span and trace IDs in span links created with OpenTelemetry Python when captured by OneAgent. Only IDs captured by OneAgent were affected, so, for example, any OpenTelemetry-based exporter would still have correct data. Only OpenTelemetry-created span links were affected, not other span links in OneAgent. Normal parent span/trace IDs were not affected. (OA-70886)
  • The OneAgent Java module now captures the http.route attribute correctly when the Spring request body validation fails. (OA-70731)
  • Fixed the EnqueuedTime attribute for Azure Event Hubs and ServiceBus to correctly report timestamps in nanoseconds instead of milliseconds. (OA-70718)
  • Fixed an issue where OneAgent's Python instrumentation called __del__ twice on wrapped objects for database, messaging, and AI SDKs. Also improved error handling in the Python Azure SDK EventHub Consumer and Experimental Python GenAI Pydantic AI features to prevent agent-related errors from affecting the monitored application. (OA-70676)
  • Improved DB2 detection. Now db2syscr processes are assigned to the general DB2 process. (OA-70656)
  • Fixed an issue where the process injection did not work when there was multi-architecture libraries installed between OneAgent updates. (OA-70551)
  • Fixed core pattern backup and configuration during OneAgent updates on Linux systems with SELinux in enforcing mode. (OA-70424)
  • Applied enrichment limits to the dt_host_metadata.properties file generated by the OneAgent. (OA-70377)
  • Fixed an issue in the Go AWS EventBridge sensors that could cause incorrect distributed trace linking when Go applications reuse input structs when calling Go AWS SDK API for EventBridge. (OA-69854)
  • Fixed duplicate log enrichment in Quarkus applications using ECS JSON logging when Java log enrichment was activated for both structured and unstructured logs. (OA-69667)
  • Improved OneAgent installer resilience to interruptions during upgrades in Kubernetes deployments. When installation files are missing, the installer now attempts recovery instead of failing. Additionally, the uninstall script is now deployed first to reduce the risk of it being missed during an interrupted upgrade. (OA-69062)
  • Vulnerability: Restricted file permissions for expected_file_checksums to prevent ownership takeover by unauthorized users. (OA-68899)
  • Resolved an issue where Apache worker processes could block and pile up (high busy-worker counts, hanging requests, and missing methodExit data) when the OneAgent companion process became unresponsive under load. A new opt-in mode makes the worker-to-companion report send non-blocking, dropping monitoring reports instead of blocking request handling. Switched off by default—switch on with the debugApacheEnableNonBlockingReportSendNative debug flag. (OA-68252)
  • Fixed a regression where the latest Dynatrace data from cross-origin iFrames were not reported in Synthetic monitoring. (DEM-32300)
  • Improved RUM JavaScript resilience when DOM APIs are overridden. (DEM-31545)
  • Fixed a technical limitation that prevented Session Replay from capturing CSS resources from inside monitored cross-origin iFrames. (DEM-30795)
Related tags
Dynatrace Platform