Added Python support for GenAI services and frameworks
OneAgent version 1.339+Dynatrace version 1.340+
OneAgent now provides automatic instrumentation for Python applications that use AWS Bedrock, OpenAI, Azure OpenAI, and LangChain.
Dynatrace captures distributed traces, logs, and GenAI-related telemetry for supported model interactions, including provider, operation, model, duration, token usage, and prompt and completion metadata where available.
You can capture prompt and completion content to debug AI and LLM interactions, analyze model behavior, and understand the performance and cost impact of calls to large language models. To enable it, go to OneAgent features and turn on Python OpenAI prompt capture [Opt-In].
Application Observability | Distributed Tracing
Azure SDK EventHub tracing in Python
We now support automatic EventHub tracing (sending and receiving messages) for the Azure SDK for Python.
Application Observability | Distributed Tracing
Automatic Azure SDK support for Java
We now support automatic tracing of the Azure SDK in Java applications (Azure SDK for Java versions 1.2.9+).
Application Observability | Distributed Tracing
Added support for Golang library apache/cassandra-gocql-driver/v2
.NET code module on AWS Lambda supports every available sensor for .NET 8 and 10 applications
The OneAgent .NET code module on AWS Lambda now supports every available sensor for .NET 8 and 10 applications.
Application Observability | Distributed Tracing
.NET code module ignores OpenTelemetry spans for technologies supported by the module
The OneAgent .NET code module now automatically ignores OpenTelemetry spans for technologies supported by the OneAgent .NET code module.
Application Observability | Distributed Tracing
OneAgent code module for IBM ESB: Tagging support for JMSReply node.
The OneAgent code module for IBM ESB (aka. IIB/IBM ACE) now supports tagging of the JMSReply (JMSClientReply) node, enabling full distributed trace propagation through message flows that reply to the destination specified in the JMSReplyTo header. This completes trace stitching across request-reply JMS scenarios without requiring any additional configuration.
Application Observability | Log Analytics
Integer, float, and fraction timestamp detection in JSON structured logs
The OneAgent Log code module now supports fractional epoch-second timestamps in JSON logs, parsed to millisecond precision with rounding.
Only the dot character (.) is treated as the fractional separator.
In addition to the previously supported string values, JSON timestamp fields with integer or floating-point numeric values are also now recognized.
Application Observability | Log Analytics
Log module self-monitoring enabled by default for Grail
The Dynatrace log module now emits self-monitoring events that deliver an environment-wide health overview for OneAgent and Kubernetes log modules. You can detect and resolve log ingest issues across distributed fleets faster, with self-service troubleshooting based on per-source status and health signals.
What's new:
Self-monitoring events for log module health and log source status, stored in Grail dt.system.events. Two event categories emitted: log source status and health‑related events.
Troubleshooting guides covering each event type, with remediation steps and query examples.
Dashboard visualizing fleet health and detected log source status—available as a downloadable package from documentation or via the upgraded built-in Log ingest overview dashboard.
Suppression mechanism to disable specific event types per configuration scope.
Where to find it:
Events in Grail dt.system.events
Dashboard package
Troubleshooting guides in our documentation.
Enabled by default for Grail; available as opt-in for Log Monitoring Classic (LMv2).
Application Observability | Services
Added file-based VCAP service support to Cloud Foundry buildpacks
We've added support for buildpacks for file-based VCAP services as described in Cloud Foundry Documentation. This means OneAgent can use file-based VCAP services for authentication.
Infrastructure Observability
Process entity in Smartscape on Grail: containerized indicator
Process entities in Smartscape on Grail have a new field, process.containerized (true/false), indicating whether the process is running in a container.
Infrastructure Observability
New field on ONEAGENT Smartscape on Grail entities
The new field dt.smartscape_source.sender was added to the ONEAGENT entity. It can be used to identify whether a host was created by a code module or an OS agent (example values: dynatrace_osagent or dynatrace_codemodule).
Infrastructure Observability
PROCESS entity extended in Smartscape on Grail
The field process.metadata.id_keys has been added to the PROCESS entity in Smartscape on Grail. The new field lists the names of fields used to calculate the process ID. The field values can be found in the process.metadata on the PROCESS entity.
Infrastructure Observability | Google Cloud
GCP information extended on HOST entity in Smartscape on Grail
We've added the following Google Cloud fields to the HOST entity in Smartscape on Grail:
gcp.zone
gcp.location
gcp.resource.type
gcp.asset.type
Infrastructure Observability | Hosts
Processes with detected OS Service now automatically reported
Processes of related OS Services (detected based on rules with “alerting” or “monitoring” enabled) are now marked as important and reported to server.
Infrastructure Observability | Hosts
Containerization type detection for Linux Kubernetes via kubelet Socket + crictl
We've added containerization-type detection for Linux Kubernetes environments using the Kubernetes socket and crictl.
Note that if you run crictl as root, OS Agent requires the cap_setuid capability. Set the capability with oneagentctl.
Infrastructure Observability | Hosts
Enriched OS Service availability metric with resource attributes
The OS Service availability metric is now enriched with process- and container-level resource attributes.
Infrastructure Observability | Hosts
Introduced a process ID metadata array field to PROCESS entity
The PROCESS entity in Smartscape on Grail now has a process.metadata.id_keys field with the keys of ID calculation parameters.
Platform | OneAgent
Support for AIX 7.3 TL4
Starting with this release, we support AIX 7.3 TL4.
Platform | OneAgent
Reduced OneAgent installation size on Windows
The OneAgent installer for Windows is 9.7 MB smaller, and a fresh installation requires approximately 75 MB less disk space.
On Windows hosts with containers, OneAgent retains files from previous versions to optimize container monitoring. As older versions are replaced over subsequent updates, the cumulative disk savings can grow up to an additional 360 MB.
Software Delivery | Configuration as Code
OneAgent installer waits up to 15 minutes for concurrent installations instead of failing with error 1618
The OneAgent EXE installer now detects when the Windows Installer engine is busy and retries automatically, waiting up to 15 minutes before exiting.
Breaking changes
Application Observability | Services
Improved consistency of database technology naming in filters
To improve consistency of database technology naming in filters, Db2 is now displayed using mixed case, aligning with IBM’s official naming convention.
Possible low‑impact breaking change: If you rely on case‑sensitive filters, dashboards, or queries that reference the previous casing, you may need to update them.
Digital Experience | RUM Web
Improved user action capture in RUM JavaScript
Improvements to user action capture in RUM JavaScript include:
User interactions that create a user action are now marked with the user_action.instance_id field.
All user actions now require user interaction to happen prior to soft navigation/XHR or fetch request.
A navigation event is no longer merged with soft navigation user action, but sent separately.
Fields user_action.hard_navigation_count and user_action.soft_navigation_count have been added.
"interaction.name" has been changed to "interaction.type".
"user_action.type": "same_view" replaces "xhr".
Infrastructure Observability | Hosts
Removed WinPcap from OneAgent installer
WinPcap is no longer supported by the OneAgent installer.
If PCAP_DRIVER=winpcap is set in your configuration or passed as a parameter, the installer will exit with an error. You must set PCAP_DRIVER=npcap or PCAP_DRIVER=disabled instead.
Any WinPcap installation previously installed by OneAgent will be automatically removed.
If you installed WinPcap manually, you'll need to uninstall it yourself.
Fixes and maintenance
General Availability (1.339.51.20260603-143443)
Fixed a potential crash on statically linked Go applications containing libc if the Go improved static injection OneAgent feature is turned on. (OA-67175)
Fixed an issue that caused rare crashes when DB nodes from Java modules were aggregated. (OA-66724)
Added Ubuntu 26.04 and Fedora 44 support for OneAgent. (OA-66674)
Improved stability for HTTP route capturing in ASP.NET Core for faulted services. (OA-66670)
Fixed a rare crash in the IBM Integration Bus (IIB) 10 monitoring plugin. A defect in the IIB 10 library causes it to write one character past the end of a supplied buffer when a monitored flow contains MQ nodes whose queue manager hostname is exactly 256 characters long. OneAgent now allocates an additional guard character to absorb this write. The crash could appear immediately upon flow execution or hours later during unrelated monitoring activity, making it difficult to correlate with the triggering flow. IBM ACE 11, 12, and 13 aren't affected. (OA-66293)
Fixed handling of full command line for non-injectable processes in process grouping rules. (OA-66032)
Improved consistency of database technology naming in filters. Db2 is now displayed using mixed case, aligning with IBM’s official naming convention.
Possible low‑impact breaking change: If you rely on case‑sensitive filters, dashboards, or queries that reference the previous casing, you may need to update them. (OA-65544)
Fixed a crash (SIGSEGV) in the OneAgent correlation engine that could occur under concurrent load when path timeout processing held stale references to recycled memory. The root cause was a use-after-free in the checkPathAges routine: after lock release, stale SubPath pointers could alias newly allocated paths, causing them to be incorrectly terminated. Path timeout operations now validate their handle before acting, ensuring stale references are discarded without affecting active paths. (OA-65434)
Fixed an issue in which, when the response had suppressed headers, OneAgent wrote some headers like Set-Cookie and Server-Timing in the first occurrence of the sequence “\r\n\r\n“ in the response body. (OA-65254)
Fixed a problem with the CRI-O/containerd runtime in which the [!dt …] injection marker couldn't be stripped from the log line. (OA-65102)
Fixed enriching process and container data by applying any fields prefixed with primary_tags from the dt_metadata file. (OA-65054)
Fixed a VerifyError affecting HikariDataSource Weld CDI proxy classes that was introduced in OneAgent 1.333 due to a change in max-stack calculation during bytecode transformation. (OA-64698)
Fixed an issue with the HTTP client sensor that caused a failed request to not be captured correctly, subsequently leading to tracing data latency. (OA-64407)
Fixed an APC synchronization issue in the Windows injection driver (oneagentmon) on driver unload. In rare cases, it caused a BSOD during OneAgent update or uninstall. (OA-64376)
Unmonitored AWS SDK service methods are now prevented from creating HTTP Client services. (OA-63348)
Vulnerability: For improved security, we've removed the batch file from the installation chain. MSI installation is now invoked directly via the MSI API. Note that this change also means there is no longer the need to escape (repeat) the % character in property values. (OA-61065)
Fixed an issue that caused Session Replay to record more sessions than the configured capture rate. (DEM-26535)
Fixed an issue where RUM JavaScript would not detect document level scrolls (DEM-25238)
Fixed an issue where start_time for mouse_over event might be incorrect (DEM-24463)
Fixed an issue that caused process group names to be missing for CICS and IMS regions, causing notebook queries to fail. (OA-66992)
The OneAgent Java for z/OS code module now enables Jakarta Servlet 5+ support by default. (OA-65860)
Fixed an issue that caused the zRemote to erroneously flag a zLocal as having high latency on a reconnect. (OA-65733)
Fixed an issue that caused the zRemote to abnormally terminate due to invalid access to a disconnected client. (OA-65609)
Fixed an issue with too frequent refreshing of certain parts UEM configuration that caused excessive memory usage in multi-process web servers. (OA-65073)
Fixed handling network adapters of type Microsoft Network Adapter Multiplexor by networkagent on Windows. (OA-64414)
Fixed the issue with mainframe traces (for example, seen in the Distributed Tracing app) showing host ID of HOST-0000000000000000. (OA-64097)
Resolved an issue where disabling and re-enabling deep monitoring on IBM App Connect Enterprise could lead to a gradual resource leak, eventually causing complete monitoring loss approximately 75 minutes after restart. OneAgent now correctly releases all internal resources during monitoring lifecycle transitions, helping to ensure uninterrupted visibility. (OA-64004)
Fixed response body capturing when a combination of WebFlux and Tomcat is used. (OA-60993)
Fixed formatting of the ActiveGate ID in data produced by Dynatrace extensions. (DAQ-23179)