Try it free

What's new in Dynatrace OneAgent 1.337

  • Release notes
  • 4-min read
  • Rollout start on May 05, 2026

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

  • Feature updates: 9
  • Breaking changes: 4
  • Fixes and maintenance: 19

Oldest supported versions

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

Support levelOldest supported version

Standard Support

1.319

Enterprise Success and Support

1.313

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

Feature updates

Application Observability

Primary and AWS fields added to OneAgent AWS Lambda deployments

Primary fields set via DT_TAGS are now added to logs and spans in AWS Lambda deployments of OneAgent. Logs and spans now include the AWS-specific attributes aws.arn, aws.region, and aws.account.id.

Application Observability | Distributed Tracing

Modernized IBM MQ sensor for .NET Instrumentation Engine v2 support with improved trace ID propagation in message headers

The IBM MQ sensor's internals have been modernized to support .NET Instrumentation Engine v2, but the behavior should be identical to the legacy version. Also, the sensor now sends trace IDs in the message header, ensuring accurate PurePath correlation. Previously, due to technical constraints, a specialized hash of the message metadata was used for this purpose (which remains as a fallback for compatibility).

Application Observability | Distributed Tracing

Go static monitoring no longer requires ptrace on Linux 3.17+

We improved Go static monitoring so it no longer requires the Linux ptrace capability. This requires Linux kernel version 3.17+; on earlier versions, it falls back to a ptrace-based approach.

Digital Experience | RUM Web

Improved runtime performance of RUM JavaScript

We’ve improved the runtime performance of RUM JavaScript by switching to more modern data structures, such as Map and Set.

Infrastructure Observability | Infrastructure & Operations

Improved IBM integration server process detection

We’ve improved the detection of the IBM integration server process (IBM ACE) to reduce false positives.

Platform | OneAgent

Support for Redis StackExchange for .NET

We’ve added tracing support for StackExchange.Redis in .NET applications.

Platform | OneAgent

Support for AWS Lambda log enrichment via DT_TAGS in log collector

We've added support for log enrichment in AWS Lambda log collector via the DT_TAGS environment variable.

Platform | OneAgent

Improved process detection on AIX for exec without fork

For already-running processes on AIX, we added detection for changing executable command or memory layout, and treat these as new process.

Platform | OneAgent

Added NuGet package for supporting .NET trimmed applications

We’ve added NuGet package support for monitoring trimmed .NET applications.

Breaking changes

Infrastructure Observability | Network

Winpcap no longer supported by OneAgent

OneAgent on Windows now requires Npcap to provide network metrics generated by Network Agent. Winpcap is no longer supported.

Platform | OneAgent

Improved Host Infrastructure Observability event titles and descriptions

Host Infrastructure Observability events now have concise, distinctive titles and detailed descriptions.

Platform | OneAgent

Azure region strings now use programmatic naming format

Azure region strings in resource attributes are now reported using programmatic naming (lowercase, no spaces). For example, New Zealand North becomes newzealandnorth.

Platform | OneAgent

Added per-PID core process metrics for worker processes (MintV2)

Core process metrics (MintV2) for Latest Dynatrace now provide per-PID visibility for worker processes in multi-process scenarios, aligned with tech-specific metrics (such as Python GC, threads, and heap). Single-process scenarios remain unchanged.

Fixes and maintenance

General Availability (1.337.5.20260403-150810)

  • Fixed problem with incorrect merging container log records from CRI-O runtime. (OA-65334)
  • Fixed an issue where the log agent could miss very short‑lived pod log files produced by the CRI‑O runtime during rapid rotation. (OA-64708)
  • Fixed an issue where AIX shutdown detection was not working correctly. (OA-64070)
  • Enhanced handling of the MSU billing for scenarios involving a single zRemote communicating with multiple zDCs. (OA-63870)
  • RxJava sensor performance has been optimized, reducing monitoring overhead. Note: Some performance impact remains depending on application code due to the nature of RxJava instrumentation. (OA-63416)
  • Added support for multiple OneAgents injection in FIPS mode. (OA-62677)
  • Fixed possibly incorrect Go HTTP latency metric values when the system clock jumped. (OA-62594)
  • Fixed an issue where the OpenTelemetry Java agent alongside OneAgent could cause spurious "Dead code detected" and StackMapTable instrumentation warnings for certain Reactor and Netty classes. (OA-61560)
  • Fixed an issue where view.url.full could potentially be incorrect for events with a duration greater than zero. (DEM-23666)
  • Fixed SFM log duplication on environments where the same extension version was used in multiple configurations of a particular Python extension. (DAQ-20549)
  • Fixed an issue in SNMP extensions where constant metrics were reported even when dimension data requiring queries were not collected. (DAQ-20312)
  • Fixed an issue in SNMP extensions where dimensions were incorrectly mapped for metrics sharing the same key. (DAQ-16843)
  • Fixed an issue where the Extensions Execution Controller failed to resume extension execution after certificate removal and re-addition. (DAQ-12171)
  • Fixed package path reporting for Go generics symbols. (OA-63156)
  • Removed potentially sensitive values such as library exception messages from certain agent error log messages in Python Oracledb, Python AWS SDK, and OneAgent SDK Python features. (OA-63039)
  • Fixed MethodNodes aggregation in the Go Cassandra sensor. (OA-62985)
  • Fixed exception handling in AsyncApiCall.end() to ensure proper logging of exception details. (OA-62805)
  • Corrected setting of the log directory permissions in the container injection. (OA-62403)
  • Fixed an issue where Nginx runtime instrumentation failed when using split debug information. (OA-62301)
Related tags
Dynatrace Platform