-
Release notes
-
2-min read
-
Published Mar 26, 2026
-
Rollout start on Apr 07, 2026
This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.335. It contains:
Digital Experience | RUM Web
New method added to RUM JavaScript API for sending custom keypress events
You can now call to send custom keypress events.
Feature updates
Application Observability
Removed non-informative PP nodes for outgoing web requests
We have removed non-informative PP nodes for outgoing web requests in the following Java HTTP clients: Apache HTTP, OkHttp, and JDK Internal HTTP client.
Application Observability | Distributed Tracing
Bottle tracing in Python
We have added Bottle tracing in Python.
Application Observability | Distributed Tracing
Follow messages with newly added Kombu tracing in Python
We have added Kombu tracing in Python.
Application Observability | Distributed Tracing
Sanic tracing in Python
We have added Sanic tracing in Python.
Application Observability | Distributed Tracing
Falcon tracing in Python
We have added Falcon tracing in Python.
Application Observability | Distributed Tracing
Monitor your applications built with Golang 1.26
We have added support for monitoring Go version 1.26.
Application Observability | Distributed Tracing
gRPC Status Code Support for Java applications
Java applications can include gRPC status in traces. This feature is turned off by default and should be enabled using the flag Java gRPC Status Code Support. Note that enabling this feature might affect gRPC streaming traces and trigger a timeout in such situations.
Application Observability | Log Analytics
Message throttling mechanism for Log module
We have introduced a throttling mechanism into the OneAgent Log module. If network transmission problems occur, the Log module limits the number of parallel messages and increases retransmission time.
Digital Experience | RUM Web
Added support for standalone Shift keypress combinations
In RUM, standalone Shift-key combinations, such as Shift+A, will now be reported if the configuration flag is set to . It is by default.
Infrastructure Observability | Hosts
Java 26 processes are now fully monitored
Java 26 processes are now fully monitored.
-
We now support LTS versions plus the last four Java versions (23, 24, 25, and 26).
-
With OneAgent version 1.335Java 22 is no longer monitored. If you are running Java 22, you can either update to Java 25+ and monitor your processes with OneAgent version 1.335, or you can keep using Java 22 with OneAgent version 1.333 and earlier.
Java 26 on Alpine Linux is not supported by OneAgent.
Infrastructure Observability | Hosts
Additional system info updated only once at OneAgent start
Data for the property is now gathered only once when OneAgent starts.
Infrastructure Observability | Hosts
Added to Smartscape entity
We have added the attribute to the Smartscape entity.
Infrastructure Observability | Hosts
Added support for OpenSUSE 16.0
OneAgent now supports OpenSUSE 16.0.
Platform | OneAgent
Support for Apache HTTP Client 5.x on Java z/OS
We now support Apache HTTP Client 5.x for Java applications running on z/OS. For details, see Mainframe technology support.
Platform | OneAgent
Added tracing support for in Node.js code module
We have added tracing support for graphql-yoga for tracing in CJS and ESM applications. For details, see Technology support.
Platform | OneAgent
Support for Apache HTTP 5.x (Java ODIN)
We have added support for Apache HTTP 5.x to Java-ODIN.
Breaking changes
Application Observability
Improved support for OpenTelemetry spans in OneAgent Java module
We have improved support for OpenTelemetry spans in the OneAgent Java module.
-
The Java module now handles OTel spans the same way that other Dynatrace code modules (Node.js and Go) already do. The behavior is semantically the same.
-
If you need to restore the previous behavior, you can re-enable it by adding the flag .
Infrastructure Observability | Hosts
OneAgent automatically discovers on AIX
OneAgent now autodiscovers on AIX as a system log, eliminating the need to create a custom log source configuration, automatically decorating logs with process group context, and allowing log ingest configuration based on process group (aligned with existing Linux behavior). remains detected on both AIX and Linux.
Impact
-
Customers with system-log ingestion enabled on AIX and with system logs written to will see additional log records ingested. This improves coverage by filling gaps in monitoring data. If the custom log source is already configured, it will remain compatible.
-
Potential breaking-change scenarios: any log ingest rules with broad matchers (for example, "ingest all logs") may begin ingesting more data than before.
Recommended customer actions
-
In the Logs app, filter for logs where the log.source attribute equals and assess relevance.
-
If necessary, refine ingest rules by adding path- or process-based matchers, applying exclusion rules to prevent unwanted ingestion.
-
Audit log ingest rules that use broad matchers (for example, rules that capture all files or all system logs).
Infrastructure Observability | Hosts
Disk Edge allows filtering based on new disk properties
Detection rules have been added, now offering disk filtering based on:
-
Disk filesystem
-
Disk type (local or remote)
-
Disk total space thresholds (above, below, or both)
Fixes and maintenance
General Availability (1.335.38.20260327-125350)
-
We have improved installation time on slow machines. (OA-61975)
-
Fixed an issue that prevented the Go Custom Service from being disabled. (OA-61396)
-
Processes with incomplete detected properties no longer receive incorrect Windows System technology. (OA-61393)
-
Removed k8s.namespace.name attribute generated by the standalone log module from system-like logs. (OA-61245)
-
Fixed case sensitivity when searching for or attributes in JSON documents. (OA-60996)
-
OneAgent was not ignoring old timestamps in fresh, JSON-structured logs. This has now been fixed. (OA-60898)
-
Fixed reporting multiple network interfaces with the same entity ID on Windows. (OA-60440)
-
Improved detection of Python processes that use non-standard command-line delimiters. As a result, identifiers for those processes may change. (OA-59776)
-
Fixed an issue where changes to USER parameter were not detected, preventing propagation of changes. (OA-58597)
-
Fixed an issue where a subclassed XHR instance would lose its subclass prototype in the prototype chain if proxy XHR wrapper was enabled on the page. (DEM-22176)
-
Added support for handling user-specific settings in RemotePluginModule. (DAQ-21395)
-
Fixed an issue in SNMP extensions where metrics were reported even when their filtered dimension data was not collected. Metrics are now emitted only when all filtered dimensions are present and meet their defined filter criteria. For details on SNMP filter behavior, see SNMP data source reference. (DAQ-19103)
-
Fixed an issue in which, if a service contained more than one invocation of a web client request within a single CICS Transaction, the service did not appear in Latest Dynatrace services. (OA-62671)
-
Fixed missing log entries when no timestamp was present. (OA-61645)
-
Fixed capturing of the AWS X-Ray tracing header in the AWS Lambda incoming sensor. (OA-61243)
-
Resolved a potential autoupdater crash that could occur when running without the required privileges (OA-61114)
-
The diagnostic statistic for the Log module now shows the correct timestamp pattern when JSON parsing is enabled. (OA-60896)
-
Fixed a OneAgent OS module issue for AiX in which the OS module collected connections from all protocols instead of only TCP. (OA-60854)
-
In the AWS SNS integration, now correctly contains the topic name, not the full ARN. (OA-60697)
-
In the Python Flask sensor, request parameter capturing no longer potentially consumes the request stream. (OA-60261)
-
We have improved cloud metadata downloads and cloud type detection for rare cases where IMDS was unreachable at OS module startup, especially on EC2 instances. (OA-58213)