This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.345. It contains:
With this release, the following are the oldest supported OneAgent versions.
| Support level | Oldest supported version |
|---|---|
1.327 | |
1.321 |
For details, see How long are versions supported following rollout?.
Application Observability
Memory dumps for .NET applications on Linux now use the .NET diagnostic IPC port (requires .NET Core 3.1+), producing standard .dmp 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
Worker threads using Secure ECMAScript (SES) lockdown() no longer cause double-instrumentation or crashes.
Application Observability | Distributed Tracing
OneAgent .NET code module monitoring of AWSSDK.DynamoDBv2 is now extended to also support version 4.0.20.0+.
Application Observability | Distributed Tracing
We now support automatic CosmosDB tracing for the Azure SDK for Python.
Application Observability | Distributed Tracing
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
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
OneAgent now supports monitoring of statically linked Go applications on AWS Lambda.
Application Observability | Distributed Tracing
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
We extend Python Azure Function support by adding new triggers: Cosmos DB, Kafka, Queue storage, and IoTHub.
Application Observability | Distributed Tracing
OneAgent now supports monitoring of the aws-sdk-go-v2/service/eventbridge Golang library.
Application Observability | Log Analytics
Dynatrace OneAgent now enriches .NET NLog with trace context, enabling seamless correlation between logs and traces in Dynatrace.
To get started, turn on the Advanced .NET Instrumentation mode OneAgent feature.
Business Analytics | Business Analytics
Business events coming from OneAgent are now enriched with metadata defined with ingest enrichment rules.
Digital Experience | RUM Web
Added support for compatibility checks between RUM JavaScript and @dynatrace/rum-javascript-sdk.
Digital Experience | RUM Web
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
The new trace context handling for RUM JavaScript adds a tp_source 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 INVALID_SET hint, and replaces them with agent-generated values.
Digital Experience | RUM Web
You can now modify the trace ID and span ID via the addEventModifier API for request events.
Infrastructure Observability | Extensions
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
Introduced support for Vinyl Cache technology after its rename from Varnish Cache.
Platform | OneAgent
Dynatrace OneAgent now automatically detects and traces Spring @Scheduled methods, eliminating the need to manually configure custom services for each scheduled task.
@Scheduled as custom methods@Async) scheduled methodsThis 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
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:
To get started, go to Settings > OneAgent features and turn on Java GraphQL [Opt-In].
Platform | OneAgent
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
OneAgent now supports status code capturing for node.js tracing of grpc and @grpc/grpc-js modules.
Platform | OneAgent
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: Modify ZDCJOB,LOG DETACH.
To attach both log stream subtasks: Modify ZDCJOB,LOG ATTACH.
Application Observability
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 /[declared unavailable by agent].
Action plan: Review metrics derived from traces for previously captured requests, for example, application throughput.
Infrastructure Observability | Infrastructure & Operations
primary_tags are now promoted only from host tagsStarting with OneAgent version 1.345, the OS Agent derives primary_tags from host tags (hostautotag.conf) rather than from host properties (hostcustomproperties.conf) at the host level.
Action plan: Verify whether primary_tags are defined via custom metadata or hostcustomproperties.conf at the host level, since these will no longer be honored after the upgrade.
Platform
Starting with OneAgent version 1.345, /etc/sysctl.conf is now the primary file for configuring the kernel core pattern when it exists on the system. If /etc/sysctl.conf is not present, 99-coredump-dynatrace.conf is written to a sysctl.d directory instead.
Action plan: If you previously relied on the sysctl.d configuration, verify your core pattern settings after upgrading.
Software Delivery | Ownership
Due to security concerns, versioned directories will no longer be removed automatically on hosts where auto-updates and process auto-injection are disabled.
/[declared unavailable by agent]. Trace-derived metrics such as application throughput may be affected. (OA-70450)ts-node symlink in Node.js code module. (OA-70194)99-coredump-dynatrace.conf in a sysctl.d directory was used to configure the kernel core pattern even when /etc/sysctl.conf existed on the system. (OA-69666)Server-Timing header was emitted twice when including the dtRpid metric. The header is now emitted only once. (OA-67244)user_action.instance_id if started during an active user action. (DEM-30881)tracestate headers to be set. (DEM-29902)