Results
Dynatrace Inc.
08/27/2026 | Press release | Distributed by Public on 08/27/2026 02:53
OneAgent release notes version 1.345
- Release notes
- 9-min read
- Published Aug 12, 2026
- Rollout start on Aug 25, 2026
This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.345. It contains:
Oldest supported versions
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
Enabled use of .NET diagnostic IPC for collecting memory dumps
Memory dumps for .NET applications on Linux now use the .NET diagnostic IPC port (requires .NET Core 3.1+), producing standard files instead of core dumps. They can be opened and analyzed directly in Visual Studio and other .NET-aware diagnostic tools, resolving a long-standing limitation for customers debugging Linux-hosted .NET services. Classic core files are produced as a backup in case of failure. If you need to enable classic core dumps, reach out to Dynatrace support.
Application Observability | Distributed Tracing
Improved compatibility with SES in worker threads
Worker threads using Secure ECMAScript (SES) lockdown() no longer cause double-instrumentation or crashes.
Application Observability | Distributed Tracing
Added support for AWS SDK DynamoDB 4.0.20.0+
The sensor now supports version 4.0.20.0+.
Application Observability | Distributed Tracing
Azure SDK CosmosDB instrumentation
We now support automatic CosmosDB tracing for the Azure SDK for Python.
Application Observability | Distributed Tracing
Add tracing support for Apache Camel v4
Context propagation is now supported for Apache Camel v4, including multi-threaded scenarios. This feature is currently available for DevOps only and requires Java Threading Flat Trace Structure. To enable it, contact a Dynatrace product expert.
Application Observability | Distributed Tracing
.NET Runtime-Async
OneAgent now supports in-process context propagation and span tracing when using .NET runtime-async. This requires the Advanced .NET Instrumentation Mode OneAgent feature to be enabled.
Application Observability | Distributed Tracing
Monitor statically linked Go applications on AWS lambda
OneAgent now supports monitoring of statically linked Go applications on AWS Lambda.
Application Observability | Distributed Tracing
Support for WebLogic 15.1.1
WebLogic thin client jar (wlthint3client.jar) is not supported. IIOP has known vendor issues in WebLogic 15.1.1; T3 is supported as a workaround for server-to-server connections only.
Application Observability | Distributed Tracing
New Python Azure Function triggers support
We extend Python Azure Function support by adding new triggers: Cosmos DB , Kafka , Queue storage , and IoTHub .
Application Observability | Distributed Tracing
Added support for Golang library aws-sdk-go-v2/service/eventbridge
OneAgent now supports monitoring of the Golang library.
Application Observability | Log Analytics
.NET NLog: Automatic log enrichment with trace context
Dynatrace OneAgent now automatically enriches .NET NLog with trace context, enabling seamless correlation between logs and traces in Dynatrace.
- Automatic trace context injection for structured NLog logs
- Opt-in trace context injection for unstructured NLog logs
- Supports NLog version 4.5 and later
Business Analytics | Business Analytics
Business events ingest enrichment
Business events coming from OneAgent are now enriched with metadata defined with ingest enrichment rules.
Digital Experience | RUM Web
Compatibility checks support between RUM JavaScript and the SDK
Added support for compatibility checks between RUM JavaScript and .
Digital Experience | RUM Web
Improved user action duration calculation
RUM JavaScript now caps a user action's duration at the configured maximum user action duration. Previously, if JavaScript execution was suspended and resumed later (for example, when a tab was backgrounded) or a custom start time was set via API, a user action could report an unrealistically long duration. Such actions are now capped to the maximum and reported as timed out.
Digital Experience | RUM Web
RUM JavaScript trace context handling
The new trace context handling for RUM JavaScript adds a field to the generated trace state, indicating whether the trace parent was set externally or by the agent. If the trace parent headers are invalid, it detects them, reports an hint, and replaces them with agent-generated values.
Digital Experience | RUM Web
Add custom trace linking for edge cases
You can now modify the trace ID and span ID via the API for request events.
Infrastructure Observability | Extensions
Improved metric enrichment consistency in Extension Execution Controller
Extension Execution Controller (EEC) enrichment of outgoing metrics with additional context now complies with data formatting rules before it reaches Dynatrace. Normalization is applied without distinction across different types of enrichment data.
-
Enrichment values attached to your metrics (for example, process and host information, custom host metadata, and related entity details) are consistently formatted to meet metric ingestion requirements, reducing the likelihood of metric rejection and improving the reliability of metric dimensions.
-
Logs and traces are unaffected. Log data continues to receive the original, unaltered enrichment values, preserving full-fidelity detail for troubleshooting. This fixes a prior inconsistency in which some log attributes were unintentionally altered.
No configuration changes are needed on your part.
Infrastructure Observability | Hosts
Added Vinyl Cache technology support
Introduced support for Vinyl Cache technology after its rename from Varnish Cache.
Platform | OneAgent
Spring Framework: Automatic tracing for @Scheduled methods
Dynatrace OneAgent now automatically detects and traces Spring methods, eliminating the need to manually configure custom services for each scheduled task.
- Automatic instrumentation of methods annotated with as custom methods
- Support for both synchronous and asynchronous () scheduled methods
- Recursive calls to the same scheduled method are suppressed, consistent with existing custom service behavior
- Supports Spring Boot 2.0 through 4.x
This functionality is currently in Early Access and is disabled by default. To enable it, enable the Java Spring @Scheduled annotated methods support feature.
Platform | OneAgent
Out-of-the-box instrumentation for Spring GraphQL
Dynatrace OneAgent now provides native instrumentation for GraphQL Java. This opt-in feature brings automatic observability to Java-based GraphQL services without requiring manual OpenTelemetry setup.
What's new:
- Automatic detection of GraphQL Java services running on Spring GraphQL
- Tracing for incoming GraphQL requests processed by the Spring GraphQL layer
- Visibility into backend calls made through GraphQL APIs
To get started, go to Settings > OneAgent features and turn on Java GraphQL [Opt-In].
Platform | OneAgent
Generate SBOM and attach attestation to classic fullstack container image
SBOM generation is now supported for the classic fullstack container image. Two variants are provided per architecture: a full internal version and a trimmed external version.
Platform | OneAgent
Status code capturing for node.js tracing of grpc and @grpc/grpc-js modules
OneAgent now supports status code capturing for node.js tracing of grpc and @grpc/grpc-js modules.
Platform | OneAgent
zDC log stream subtasks can be restarted during runtime
We've introduced two new commands to detach and attach log stream subtasks. These are useful if the subtask unexpectedly terminated, but you don't want to restart the entire zDC.
-
To detach both log stream subtasks: .
-
To attach both log stream subtasks: .
Breaking changes
Application Observability
Corrected ASP.NET Core URL exclusion rules
Starting with OneAgent version 1.345, URL exclusion rules are correctly applied to ASP.NET Core requests, and requests are no longer captured and shown as .
Action plan: Review metrics derived from traces for previously captured requests, for example, application throughput.
Infrastructure Observability | Infrastructure & Operations
Starting with OneAgent version 1.345, the OS Agent promotes from host tags () and no longer from host properties () at the host level.
Action plan: Verify that you don't have custom alerting rules or charts based on coming from at the host level.
Platform
Improved kernel core pattern configuration priority
Starting with OneAgent version 1.345, is now the primary file for configuring the kernel core pattern when it exists on the system. If is not present, is written to a directory instead.
Action plan: If you previously relied on the configuration, verify your core pattern settings after upgrading.
Software Delivery | Ownership
Removed legacy migration mechanism of versioned directories
Due to security concerns, versioned directories will no longer be removed automatically on hosts where auto-updates and process auto-injection are disabled.
Fixes and maintenance
General Availability (1.345.6.20260724-152956)
- Fixed a configuration issue where CICS and IMS configuration did not flow correctly to the mainframe from the tenant. (OA-71898)
- Improved .NET process technology detection on Linux. (OA-71727)
- Corrected the metrics on the Azure Service Bus consumer side to avoid false positive alerts. (OA-71647)
- Fixed an issue with .NET process detection, causing missing process type and technology for some .NET processes. (OA-71375)
- Fixed BOSH BPM detection for newer runit-based versions. (OA-71339)
- Fixed a crash in the zRemote due to IMS Address Space access not being synchronized. (OA-71235)
- Disabled tracing of CICS transactions due to an error in the zRemote configuration handling. (OA-71003)
- Fixed MB Agent not being injected into IntegrationServer process on AiX. (OA-70657)
- Fixed a socket file descriptor leak in zRemote when rejecting zDC connections, which could exhaust file descriptors and block new inbound connections. (OA-70584)
- Fixed the detection of network disk stats in Windows when a network share is used in a different logon session. (OA-70469)
- Fixed URL exclusion rules not being applied to some ASP.NET Core requests, causing them to appear as . Trace-derived metrics such as application throughput may be affected. (OA-70450)
- Fixed OS Agent performance issue that was disrupting host monitoring on some OpenShift environments. (OA-70376)
- Added support for symlink in Node.js code module. (OA-70194)
- Added a fix to prevent SIGSEGV from happening when executing a gRPC call with a static metadata argument. (OA-69725)
- Updated Babel to a version that mitigates CVE-2026-49356. (OA-69713)
- Processes grouped by process grouping rules now have the correct injection status visible. (OA-69693)
- Fixed an issue where in a directory was used to configure the kernel core pattern even when existed on the system. (OA-69666)
- Fixed a deadlock at application startup that could occur when the OneAgent .NET code module and third-party security software is present. (OA-69562)
- Fixed OS Service availability event DQL query. (OA-69554)
- Fixed an issue where Log Monitoring (app-log-content-access) could be unexpectedly disabled after a OneAgent upgrade due to a configuration migration edge case. (OA-68949)
- Corrected the executable name, executable path, and command-line parameters of the PostgreSQL process when started using the pg_ctl command. (OA-68858)
- Fixed an issue where the link insertion area was not closed correctly because introspection was triggered twice, once for the class and once for its proxy, causing a conflict. Proxy classes of are now excluded from introspection, and a serial number check was added to ensure the link insertion area closes reliably. (OA-68856) (OA-68856)
- Fixed an issue where Java Lambda functions monitored by OneAgent timed out and lost traces due to another sensor not correctly clearing its state from the main thread. (OA-68569)
- Fixed overlapping text in Windows installer finish dialog window. (OA-67913)
- Vulnerability: Dynatrace Log Module Container Image is now based on Debian 13 Distroless Image (OA-67779)
- Fixed an issue where the header was emitted twice when including the metric. The header is now emitted only once. (OA-67244)
- Aligned the Java DynamoDB JSON anonymizer logic with the Node.js implementation. (OA-66908)
- Fixed an issue where some events might be missing if started during an active user action. (DEM-30881)
- Fixed a technical limitation that prevented Session Replay from capturing CSS resources from inside monitored cross-origin iframes. (DEM-30795)
- Fixed an issue where enabling gen2 Angular alongside basic XHR caused duplicate headers to be set. (DEM-29902)
- Fixed a compatibility issue between airgap.js and the XMLHttpRequest module. (DEM-29698)
- Improved handling of logs timestamp in the Extension Execution Controller (EEC). (DAQ-26848)
Dynatrace Inc. published this content on August 27, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on August 27, 2026 at 08:54 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]