Dynatrace Inc.

02/10/2026 | Press release | Archived content

OneAgent release notes version 1.331

  • Release notes
  • 1-min read
  • Rollout start on Feb 10, 2026

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

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

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

Feature updates

Application Observability

Introduced resource attribute enrichment

OneAgent now enriches telemetry data at the source with the following:

  • Primary fields: Standardized metadata from the Semantic Dictionary, along with cloud and Kubernetes metadata (when available), including , , and .

  • Primary tags: Customer-defined key-value tags applied across all signal types. You can define your own primary tags to support specific use cases better.

All primary fields and primary tags are added as top-level fields for metrics, spans, logs, business events, and Smartscape entities. This enables additional use cases in Latest Dynatrace, such as routing, bucket assignment, security, cost allocation, segmentation, and alerting.

Resource attribute enrichment is available only for Latest Dynatrace.

Application Observability | Distributed Tracing

Added support for Pika in Python

You can now benefit from the new automatic instrumentation for the Pika library in Python.

Application Observability | Distributed Tracing

Monitor Go gRPC 1.77 with Go code module

We now support the monitoring of gRPC-Go v1.77.

Application Observability | Distributed Tracing

Added Go SNS publisher Early Adopter

To enhance observability of AWS services, we added the Go SNS publisher feature.

The Go SNS publisher is available as an Early Adopter release. It allows monitoring SNS publish calls made via the API.

Application Observability | Log Analytics

Improved timestamp parsing in JSON structured logs

We extended the list of valid timestamp keys and adjusted the list of supported timestamp patterns for JSON-formatted logs.

Digital Experience | RUM Web

Improved RUM trace correlation for page loads

OneAgent sends trace information back to the browser and the local RUM JavaScript. This way, page load requests, as well as other requests where it's impossible to set W3C trace-context headers, are still linked in Grail. As a result, significantly more RUM request events become visible in the page load waterfall in Experience Vitals. Additionally, these RUM requests can be linked to backend traces using DQL, but only when such traces are available.

Infrastructure Observability

Added tmpfs file system support for Linux environments

It's now possible to detect and monitor tmpfs file systems on Linux hosts. With this change, you get visibility into in-memory file systems used by modern applications, enabling capacity insights, anomaly detection, and problem correlation in the Disk Analysis and Host views.

Infrastructure Observability | AWS

Improved visibility into V1 of AWS SDK for Java

The Java AWS SDK client feature now enhances distributed traces with visibility into the asynchronous operations of AWS SDK V1 clients.

Infrastructure Observability | Hosts

Introduced limits for MintV2 dimensions

We've introduced limits on the number of dimensions for MintV2:

  • Up to 100 dimensions are added in total.
  • Predefined resource attributes are added first.
  • User-defined resource attributes follow, up to 40% of the total limit.

Infrastructure Observability | Infrastructure & Operations

Added support for Windows 11 25H2

With this release, we added support for Windows 11 version 25H2.

Platform

Added support for Fedora 42

We now support Fedora Linux 42 .

Platform | OneAgent

HttpUrlConnection tracing for z/OS Java module

We now support automatic tracing of outgoing web requests via HttpUrlConnection, for both asynchronous and synchronous requests.

Platform | OneAgent

Added support for AlmaLinux OS 10

With this release, we started supporting AlmaLinux OS 10 (codename "Purple Lion").

Breaking changes

Application Observability

URL/RPC-based reduction rules apply regardless of sampling threshold

Previously, OneAgent applied URL/RPC reduction rules only when the sampling threshold required sampling. When OneAgent was capturing all requests, the reduction rules were ignored. With this release, URL/RPC reduction rules (for example, "reduce by 50%") are enforced regardless of the current sampling threshold. Reduction rules decrease the number of sampled requests that match the specified URL or RPC pattern.

Reason for this change

  • You rely on reduction rules to lower traffic for specific requests independently of global thresholds. Enforcing these rules consistently makes more capacity available for more important requests.
  • Reduction rules are applied independently of load. For example, a 50% reduction attempts to halve the number of matching requests, even if OneAgent could otherwise sample all of them.
  • Top-X/threshold logic continues to apply: When the overall capacity is constrained, "Top-X" computations may further lower the effective sampling rates for reduced rules so that the higher-priority rules ("important requests") can be favored.

Compatibility and impact

  • This is a breaking change in trace sampling behavior. Results for URL/RPC reduction rules may differ from previous OneAgent versions.
  • If you previously relied on the old behavior (that is, reductions applied only when sampling was constrained), you may now see fewer samples for reduced URLs/RPCs.

Fixes and maintenance

Resolved issues in this release (OneAgent)

  • Fixed an issue in which the property was missing in some app-only deployment cases for the process level. (OA-60387)
  • Fixed a zRemote crash caused by configuration updates. Previously, zRemote could experience a race condition when a process group configuration was handled immediately after a sub-agent unregistration. This issue has now been resolved, and the race condition no longer occurs in this scenario. (OA-58985)
  • Changed the setting permission to for the file when the file doesn't exist. (OA-58559)
  • Vulnerability: Fixed uncontrolled search path vulnerability for Windows that can lead to limited privilege escalation for a local user. (OA-58438)
  • Fixed redundant escape characters in the reported command line for processes. (OA-57812)
  • Fixed the incorrect placement of enriched data for JBoss LogManager. Previously, some log enrichment patterns that contained instead of were not recognized. As a result, enriched data was inserted before the timestamp, making the logs difficult to read. Now the enriched data is positioned correctly-either before the message or at the end of it. (OA-57641)
  • Improved the performance of the OneAgent host module when an excessive number of Linux system processes were running on the host. (OA-57049)
  • Fixed directory pattern normalization for Windows OS. Previously, it was not possible to configure and provide logs from the main disk directory. This issue is now resolved. (OA-56777)
  • Fixed handling of mounted files and environment variables when the parameter is used in OneAgent container deployment. (OA-56648)
  • Fixed the incorrect field for business events. Previously, when an ignored trace was started, the field for some business events was initialized with the value instead of a random value. We fixed this issue. (OA-56571)
  • Fixed an installer download issue when using an HTTP proxy in containerized OneAgent deployments. (OA-56031)
  • Fixed an issue where OneAgent would send navigation events with a duration of when a page load was incomplete. (DEM-20493)
Dynatrace Inc. published this content on February 10, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on February 20, 2026 at 10:35 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]