OneAgent release notes version 1.311

Rollout start: Apr 8, 2025

With this release, the following are the oldest supported OneAgent versions.

Support level
Oldest supported version

For details, see How long are versions supported following rollout?.

Breaking changes

Infrastructure Observability | Hosts

Ignore empty grouping environment variables

The following environmental variables will be regarded as non-existent if they are left empty:

  • DT_CLUSTER_ID
  • DT_NODE_ID
  • DT_HOST_ID
  • DT_ENVIRONMENT_ID

Infrastructure Observability

OS Services monitoring policy now requires detection rule

New or modified OS Services monitoring policies require defining at least one detection rule. Preexisting policies will be honored without changes.

Detection rules support the additional $match() operator.

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

End of support

For more information, see End of support announcements.

New features and enhancements

Infrastructure Observability | Hosts

Added support for template OS Services in Linux

Template services are now supported on Linux systems.

When Dynatrace detects templated service file (for example, postgresql@.service), it will monitor instances of that service (for example, postgresql@14-main.service and postgresql@14-second.service).

Application Security | Vulnerabilities

Go support for RVA and RAP

Go technology is now available for Runtime Vulnerability Analytics (code-level vulnerability detection) and Runtime Application Protection (attack protection).

Action required

With this release, preview customers for Go technology (RVA and RAP) need to upgrade to OneAgent version 1.311 to reactivate this functionality. After that, no further configuration is necessary.

Application Observability | Distributed Traces

Kafka (Confluent Golang Client) 1.9 - 2.8 (Go Module)

Added support for Apache Kafka message monitoring Confluent Golang Client.

Resolved issues

General Availability (Build 1.311.70)

The 1.311 GA release contains 27 resolved issues.

General

  • Corrected an issue in which reading the declarative process group settings could fail on Windows in certain cases. (OA-45645)
  • Fixed loss of process deep-monitoring visibility after attempts to report very large PurePaths from a worker process. (OA-42894)
  • Fixed an issue in which `dt.process_group.detected_name` was not present (for example, in Notebooks) if the container group ID was missing. (OA-43156)

Logging module

  • Optimized log reading time in case of a remote drive with low response time, where a directory with a very high number of log files is monitored by the OneAgent logs code module. This fix also reduces the time delay for log ingesting. (OA-43965)
  • Fixed tracking of active container logs for Kubernetes if 'Settings > Log module feature flags > Collect all container logs' is enabled and Dynatrace stops ingesting logs. It was leading to disk space not being reclaimed due to outstanding file handles to already deleted container logs. (OA-45092)
  • When custom logs with wildcards match multiple files, some of which don’t match log security rules, the log module should process the remaining files normally. (OA-42837)

OpenTracing Java

  • AWS Lambda Java: Fixed an issue where traces were missing resource information if the OpenTelemetry integration was used before the first Lambda handler method invocation started. (OA-43042)

Java

  • Added context propagation for `Thread.startVirtualThread(...)`, `Thread.ofVirtual().unstarted(...).start()`, and `Thread.ofVirtual().factory().newThread(task).start()`. (OA-42978)
  • To prevent affecting application when started with a combination of -Xshare:on / -Xshare:auto / -XX:SharedArchiveFile, they are now completely removed and the application is started with -Xshare:off instead, as we do not support instrumenting Java applications with shared classes. (OA-43127)
  • Fixed a problem in Weblogic T3 RMI sensor for newer version Weblogic 14.1.2. (OA-40980)

PHP

  • Resolved an issue where an ExceptionAttachment's stacktrace could expand limitlessly. (OA-42896)
  • Fixed a bug in which disabling PHP Framework Sensors via a disable debug flag might not have worked properly. (OA-42251)

AI causation engine

  • Fixed issue in which configured URL-based sampling rules didn't work if OneAgent used additional entry point information, like information for application detection. (OA-44027)

Mainframe

  • Resolved issue in which, when many IMS-dependent regions from more than one zDC were un-registering at roughly the same time, the zRemote could crash. (OA-44034)
  • Resolved an issue in which the zRemote would terminate unexpectedly when an address space disconnects and its related resources are released. (OA-45129)
  • Resolved an issue in which the zRemote was not properly ending faulty paths with the internal correlation engine, which would then cause that engine to run out of resources, since the faulty paths were not closed. (OA-43743)

Node.js

  • Resolved an issue in which the Node.js code module caused an infinite recursion on patching the npm module `node-worker-threads-pool`, which led to application crashes. (OA-44411)
  • Fixed assertion failure and lost traces due to an undefined filename from eval() by setting code.filepath to "<no-filename>". (OA-43872)

OS module

  • Fixed an issue with bulk process removal from process group (for example, on process exit) that caused OS module freeze and high CPU utilization. (OA-43147)
  • Fixed an issue that caused monitoring loss of some alias OS services on Linux machines with systemd versions 219-245. (OA-44263)
  • Limited privileges of reading processes on Windows to read only. (OA-42810)
  • Fixed OneAgent OS module crashes related to no longer existing processes. (OA-42065)
  • Fixed a bug that could close a socket handle owned by a random remote process (Windows). (OA-44288)
  • Fixed metrics selection DQL for connection fail rate event. (OA-44434)
  • OneAgent will now send correct metrics keys: `dt.process.network.packets.base_re_tx_agg` for `dt.process.network.packets.base.re_tx.aggr`, and `dt.process.network.packets.base_re_rx_agg` for `dt.process.network.packets.base.re_rx.agg`. (OA-43155)

Apache

  • Fixed an issue where using mod_remoteip and mod_security2 caused incorrect client IP detection. (OA-43678)

Python

  • Fixed an issue where OneAgent could launch copies of the monitored application (using the Linux fork system call) when the Python code module was injected and then failed to initialize. The problem did not occur for retry-able issues. For example, a network error when connecting to Dynatrace would not cause the issue. The problem can be circumvented on older OneAgent versions by setting the environment variable `DT_PYTHON_FORKABLE` to `0` or `false`. As a consequence of this workaround, if the monitored application forks, the forked child processes can no longer be monitored. (OA-44354)

Update 72 (Build 1.311.72)

This is a cumulative update that contains all previously released updates for the 1.311 release.

OneAgent for Android

General Availability (Build .311)

The .311 GA release contains 4 resolved issues.

ComponentResolved issues
Android3
Session Replay for Android1

Android

  • Aligned `dt.rum.session.id` from BizEvents with other events to make it queryable. (DEM-6093)
  • Fixed an issue where the root detection logic could lead to an Application Not Responding error. (DEM-6057)
  • Changed ID generation to avoid session merging of unrelated applications. (DEM-6061)

Session Replay for Android

  • Fixed problem using Webview with Session Replay enabled. (DEM-6547)

OneAgent for iOS

General Availability (Build 8.311.1)

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

OneAgent for JavaScript

General Availability (Build 1.311.3)

The 1.311 GA release contains 1 resolved issue.

JavaScript

  • Fixed an issue in the Session Replay module of the JavaScript agent that would prevent the browser's garbage collector from freeing the memory of nodes that have been removed from the page. (DEM-6163)