OneAgent release notes version 1.269

Rollout start: Jul 5, 2023

With this release, the oldest supported OneAgent versions are:

Standard Support

Enterprise Success and Support

1.251

1.245

Technology support

Definition of the technology support version schema with examples:

Major version 5 is supported
- Major version 5 is supported, including all of its minor versions like 5.1 and 5.2
- Other major versions are not supported like 6 and 7
Minor version 5.1 is supported
- Minor version 5.1 is supported, including all of its patch versions like 5.1.1 and 5.1.2
- Other minor versions are not supported like 5.2 and 5.3
Patch version 5.1.1 is supported
- Patch version 5.1.1 is supported
- Other patch versions are not supported like 5.1.2 and 5.1.3
Version range 5.1 – 5.3 is supported
- Minor versions 5.1, 5.2, and 5.3 are supported, including all of their patch versions like 5.1.1, 5.2.1, and 5.3.1
- Other minor versions are not supported like 5.0 and 5.4
The minimum required version is 5+
- All major, minor, and patch versions starting from version 5 are supported, like 5, 5.1, 5.1.1, and 6

New technology support

For more information, see New technology support.

End of support

For more information, see End of support announcements.

OneAgent SDK for Node.js 1.0, 1.1, 1.2, 1.3. Announcement
Windows Desktop 8.1 (OS module)
- Vendor end of support: Jan 10, 2023
Windows Server 2008 R2 (OS module)
- Vendor end of support: Jan 14, 2023

New features and enhancements

Improved attack detection

Application Security | Attacks

Improved attack detection for Command injections and JNDI injections.

Entry point information for code-level vulnerabilities

Application Security | Vulnerabilities

Every detected code-level vulnerability now shows all application paths that let a user potentially exploit this vulnerability. This helps developers and security engineers with evaluating the vulnerability and verifying a potential fix.

The code-level vulnerability details page now shows the entry points (URLs/paths) and the user-supplied inputs (such as HTTP parameters) that can be abused.

Enabled event ingest on OneAgent localhost interface

Infrastructure Monitoring | Events

Event ingest (similar to log and metric ingest) is enabled on the OneAgent localhost interface.

Resolved issues

General Availability (Build 1.269.154)

The 1.269 GA release contains 30 resolved issues (including 2 vulnerability resolutions).

Component	Resolved issues
All modules	2
Infrastructure Monitoring	3 (2 vulnerabilities)
OS module	10
OpenTracing module	2
Java	2
.NET	5
PHP	1
Go	2
NGINX	1
IIS	1
Node.js	1

All modules

The "process must be restarted" message is no longer displayed for .NET Core processes if .NET Core monitoring is disabled. (OA-16828)
Injection of the OneAgent IIB code module is no longer reported as failed for platforms where it is not supported. (OA-17439)

Infrastructure Monitoring

Vulnerability: Tightened security for EEC local host communication. (EXT-5010)
Vulnerability: In response to CVE-2023-24329, updated Extensions Execution Controller (EEC) Python runtime to version 3.10.12. (EXT-5378)
Python extension (Extensions 2.0) can now be executed on Windows Server 2008. (EXT-5093)

OS module

Fixed an issue where df did not spawn a process correctly even after it stopped being spawned, which could result in disk metrics not being updated. (HOST-3155)
Fixed issue where, from time to time on network shares, there were spikes of usage that showed throughput in PiB/s. (HOST-3218)
Fixed an issue where disk exclusion rules were applied only to local disks. (HOST-3221)
Fixed high agent CPU usage on hosts with high network traffic. (HOST-3156)
Fixed Node.js technology detection for the process running inside a container. (HOST-3139)
Excluded administrative and local shares from statistics for network shares. (HOST-3219)
Network Agent no longer sniffs by default on Windows Hyper-V switches. (DMX-3727)
Corrected permissions on the `ruxithost.id` file to allow everyone to read it. (HOST-2332)
OneAgent OS module will now time out after 2s when stuck on WMI class access. (HOST-3122)
Fixed an issue in which the reported CPU utilization of a single process could be higher than the CPU utilization of the entire host on Windows. (HOST-2500)

OpenTracing module

When "Envoy Istio Sidecar monitoring" is deactivated, OneAgents in sidecars no longer send distributed traces in newer Istio versions. For most use cases, we recommend using general process monitoring rules or container injection rules to control which envoys to monitor instead. These will also improve performance by not injecting the OneAgent in cases where monitoring is not desired. (OA-16958)
Envoy: fixed `overwritten1.http.status_code` occurring in Grail. For Envoy spans, in addition to `http.status_code`, a stray attribute `overwritten1.http.status_code` was occurring. Now only one `http.status_code` (type integer) occurs. (OA-17243)

Java

String attribute values and span event values are now correctly truncated using the limit configured via `sensor.stringTruncationLimit.spanattribute.value`. (OA-16907)
Resolved an issue that, after OneAgent upgrade, caused a NullPointerException in jdk.internal.net.http.HttpClient when lowercase headers for X-dynaTrace were present. (OA-18008)

.NET

Improved attack detection for SQL injections. (OA-16754)
Improved stability of the .NET code-level vulnerability/attack evaluation OneAgent feature. (OA-18007)
Improved robustness of OneAgent version detection for .NET Core. (OA-18430)
Improved queue name detection for OneAgent code module for .NET MSMQ monitoring. (OA-17904)
Improved OneAgent .NET code module stability following the Microsoft security update for .NET framework 3.5. (OA-18223)

PHP

Resolved an issue that caused a `500 internal server error` when signing in with PHP deep monitoring enabled. (OA-18507)

Go

Fixed a possibly missing Go web service if capturing all HTTP headers is enabled. (OA-16189)
Resolved an issue in which the Go web service name was missing when a net/HTTP server address was not configured. (OA-15942)

NGINX

NGINX instrumentation has been updated for currency with NGINX 1.25. (OA-17247)

IIS

When OneAgent startup fails to check the IIS Thread Pool Library (w3tp.dll) signature, rather than throwing an exception, the problem is now logged. (OA-12746)

Node.js

Corrected an issue that sometimes caused OneAgent to fail to retrieve the MongoDB hostname from the configuration URL in calls to a MongoDB database, which resulted in those calls appearing as unexpected services in the Dynatrace web UI. (OA-16588)

Update 166 (Build 1.269.166)

This cumulative update contains 3 resolved issues and all previously released updates for the 1.269 release.

Component	Resolved issues
.NET	2
OS module	1

.NET

Improved robustness of OneAgent version detection for .NET Core. (OA-18430)
Improved stability of the .NET code-level vulnerability/attack evaluation OneAgent feature. (OA-18405)

OS module

Disabled Windows network drive monitoring in response to API hanging in certain scenarios. (HOST-3206)

Update 180 (Build 1.269.180)

This cumulative update contains 2 resolved issues and all previously released updates for the 1.269 release.

Component	Resolved issues
.NET	1
Node.js	1

.NET

AspNet sensor: improved handling for retrieving context in ASP-hosted WCF apps. (OA-19004)

Node.js

Fixed a memory leak caused by the Node.js code module, which was introduced by a module-internal optimization (since reverted). (OA-19275)

OneAgent for Android

General Availability (Build 8.269.1)

General Availability (Build 8.269.1)

The 8.269 GA release doesn't contain any user-facing resolved issues.

OneAgent for iOS

General Availability (Build 8.269.1)

General Availability (Build 8.269.1)

The 8.269 GA release contains 2 resolved issues.

OneAgent for iOS

Improved Podspec compatibility. (RUM-11514)
Fixed priority inversion issue when canceling an action. (RUM-11299)

OneAgent for JavaScript resolved issues

General Availability (Build 1.269.106)

The 1.269 GA release contains 4 resolved issues.

Component	Resolved issues
JavaScript	3
Session Replay	1

JavaScript

Fixed a bug where if a Request object was used in a fetch call, the agent did not set any correlation headers on it. (RUM-11308)
Fixed issues with "sendEvent" working with generated objects. Objects generated via a class or instantiated with "new" can now be sent using "sendEvent" and "sendBizEvent" APIs. (RUM-11430)
Fixed an issue where a call to `dtrum.getAndEvaluateMetaData()` would provide a stale "info" property about the captured value, causing ambiguous results. (RUM-11139)

Session Replay

Fixed a Session Replay issue that caused the initial value of a select HTML element not to be displayed correctly when replaying a session. (SR-2309)

Update 217 (Build 1.269.217)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.269 release.

JavaScript

Fixed an issue where the regex provided for setting the x-dtc header was ignored when matching against the host name for same-origin XHR/fetch requests. (RUM-11838)