This page showcases new features, changes, and bug fixes in Dynatrace OneAgent version 1.343. It contains:
Application Observability | Distributed Tracing
We have introduced automatic Azure SDK tracing support for:
With this release, the following are the oldest supported OneAgent versions.
| Support level | Oldest supported version |
|---|---|
1.325 | |
1.319 |
For details, see How long are versions supported following rollout?.
Application Observability
The OneAgent code module for Java now enriches distributed traces with information about feature flag evaluations of the OpenFeature SDK.
Application Observability
The virtual file dt_metadata_e617c525669e072eebe3d0f08212e8f2.json/properties now contains Smartscape identifiers calculated by the Dynatrace OneAgent.
These can be used by applications to enrich their data and ensure the data is correctly associated with Smartscape entities.
For details, see Enrichment Files.
Application Observability | Distributed Tracing
We have extended instrumentation for Azure Functions (tracing, log correlation) for the Flex Consumption Plan for Linux for Python.
It supports the following trigger types (version 4.x):
Application Observability | Distributed Tracing
We have extended instrumentation for Azure Functions (tracing, log correlation) with:
Application Observability | Distributed Tracing
We have added tracing for Python Azure Functions on the Azure Flex Consumption Plan for Linux.
Application Observability | Distributed Tracing
Support for .NET applications now includes the gRPC status code in traces.
Application Observability | Distributed Tracing
The OneAgent feature “Instrument .NET Single-File Self-Contained applications“ allows you to monitor single-file, self-contained .NET applications. This applies to framework-dependent deployment and self-contained applications.
Application Observability | Log Analytics
OneAgent now supports the rotation patterns in which the files are compressed or removed immediately after the rotation. The supported scope is limited to Linux and only log files that are located on local drives.
Application Security
Now hashes are available for classic .NET software component monitored entities, and can be queried via DQL:
fetch dt.entity.software_component |fields packageName, softwareComponentVersion, softwareComponentFileHashes
This returns rows like:
{"packageName": "newtonsoft.json","softwareComponentVersion": "13.0.4","softwareComponentFileHashes": {"SHA1": "420b9c95d22126470efd9e36c258ed3b727dcc19"}}
Data Observability
“db.cosmosdb.request_charge” attribute valuesCorrected summarizing of the “db.cosmosdb.request_charge” attribute values of aggregated nodes/spans.
Digital Experience | RUM Web
OneAgent now captures actions for your users' hard navigations.
Infrastructure Observability | Extensions
The Extension Execution Controller now accepts a dot-separated fractional part on Unix epoch seconds (for example, 1772778391.123456), rounded to the nearest millisecond, both as JSON
strings and JSON floating-point numbers.
Platform | OneAgent
We’ve added tracing support for ServiceStack.Redis in .NET applications.
Platform | OneAgent
OneAgent now enriches telemetry data at the source based on a central enrichment configuration defined in the platform. You can define rules that conditionally apply primary tags, Cost Allocation (dt.cost.costcenter, dt.cost.product), and dt.security_context to all data from matching entities.
IF <condition on input fields> THEN enrich with <fields and values>. Conditions are expressed with DQL matcher functions (equality, phrase, and existence checks) and support NOT, OR, and AND operators.dt.host_group.id) and OneAgent resource attributes such as host.name, host.tags.<key>, process.custom_metadata.<key>, and dt.process_group.detected_name.Enrichment is applied to all data generated by a matching entity: metrics, spans, logs, Davis events, and Smartscape entities (HOST, DISK, NETWORK_INTERFACE, CONTAINER, PROCESS). Configuration is fetched from the platform on startup and refreshed periodically, so changes apply without an agent restart.
Platform | OneAgent
Added support for trimmed containers and self-contained .NET applications.
The Instrument .NET Single-File Self-Contained applications OneAgent feature allows you to monitor single-file, self-contained .NET applications. This applies to framework-dependent deployment and self-contained applications.
For details, see available packages on Dynatrace NuGet profile.
Platform | OneAgent
The OneAgent NGINX module now supports Kong Gateway Enterprise versions 3.10–3.14. Runtime instrumentation must be enabled by setting the environment variable DT_NGINX_FORCE_RUNTIME_INSTRUMENTATION=1 when starting Kong (see NGINX runtime instrumentation documentation).
host.tags and host.custom_metadata fields in the agent's Identification Message resource attributes (for example, host.tags.dt.security_context instead of dt.security_context). This inadvertently broke downstream consumers that relied on the original, non-prefixed key names, affecting security context enrichment on metrics and Smartscape, cost allocation attributes, and general metric filtering by tag value. Both the prefixed and non-prefixed variants of all host.tags and host.custom_metadata fields are now written into the Identification Message resource attributes simultaneously, restoring compatibility while preserving the new prefixed format. A debug flag is also available to fully revert to the old behavior (non-prefixed keys only) without requiring additional backports. (OA-70727)VCAP_APPLICATION was present but did not contain a valid JSON object. (OA-70001)__oa.attr2att.trigger_mappers attribute set to false on every generic Azure SDK span,40-coredump-dynatrace.conf to 99-coredump-dynatrace.conf worked for fresh installations but failed for auto update. (OA-69073)len) to fail when called on the event list passed to a user callback function. (OA-68632)If-None-Match header to be incorrectly validated in Spring Framework 6.1+. (OA-68606)NullReferenceException. Now, instead of crashing, the empty destination field is displayed. (OA-67806)/etc/sysctl.conf from backup or remove the core pattern entry when no backup existed. Now the installer removes the core pattern entry from /etc/sysctl.conf, or restores its value from backup if one exists. (OA-67618)libc that could occur if the Go improved static injection OneAgent feature was turned on. (OA-67175)dtuser to root. Hook files are now always owned by root and protected against symlink attacks. (OA-66988)--require=A or --require "A" could trigger a problem in the Next.js framework. This issue caused Next.js to transform the argument into an invalid form, for example, --require "A A" (since only one file per require is allowed), which in turn caused child processes or worker threads to fail on startup. This mitigation prevents crashes that could otherwise appear to be caused by OneAgent. (OA-66693)zos.total_general_purpose_processors was not populated (returned null) on z/OS HOST entities. (MGD-12807)Google Chrome) could unexpectedly revert to the raw executable filenames (for example, _chrome.exe_) shortly after a Java or .NET agent was detected in a co-located process. The affected name would persist until the next full process discovery cycle. Now the display name is correctly preserved. (OA-67719)