OneAgent release notes version 1.315

  • Release notes
  • 4min
Pre-release information

This is an ongoing summary of changes in this planned release. Check back here at GA for the final version.

Rollout start: Jun 3, 2025 (planned)

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

Application Observability

Suspend tracing for LPARs with inactive SMF U86 exit

As part of our requirements, SMF U86 exit must be active.

  • If it's not, OneAgent for z/OS will deactivate tracing for affected LPARs after 12 hours.
  • Once the exit is active, tracing will be reactivated again.

To verify that the SMF U86 exit is active, run the following command:

D SMF,O

Look in the command output for (EXITS(IEFU86)).

  • If you find this, the SMF U86 exit is active.

  • If you don't find this, you need to add it to your SMFPRMxx parmlib member.

    SUBSYS(STC,EXITS(IEFU86)

    Then enable it.

    D PROG,EXIT,EN=SYS.IEFU86,DIAG

For more information, see Install the zDC subsystem.

Application Observability | Distributed Traces

Subagent-specific configurations

This release closes some gaps between the subagent-specific settings in the web UI and OneAgent for z/OS. This makes it possible to make settings specific to subagents as far as they apply to the zAgent.

Your default zRemote-wide settings should not be impacted because of this change, but please be aware of the possibility that changes to subagent settings you might have made in the past become active with this update.

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

Databases | DB2 monitoring on z/OS

Phase 1 of DB2 monitoring on z/OS

In Phase 1 of DB2 monitoring on z/OS, the following key metrics are now collected:

  • CPU metrics

    • CPU time for DB2 subsystem
    • CPU time for DB2 MSTR
    • CPU time for DBM1 address space
  • Connection metrics

    • Total number of active connections
    • Number of outbound connections from DB2 to remote site
    • Number of inbound connections to DB2 from remote site
    • Number of failed connections
  • zIIP time

  • Number of EDM pool requests

  • Number of cache hits

Application Observability | Distributed Traces

Alpine Linux (musl libc) on ARM64 for containers (Apache and PHP modules)

Dynatrace now supports monitoring of Alpine Linux (musl libc) on ARM64 for containers (Apache and PHP modules).

Infrastructure Observability | Hosts

Hostname parameter based on definition from the Semantic Dictionary

The hostname parameter and host.name resource attribute now represent the same value based on the definition from the Semantic Dictionary.

Logs

Optimized handling of log sources with many files

We have optimized the handling of log sources that have a very high number of files.

Resolved issues

General Availability (Build 1.315.58)

The 1.315 GA release contains 21 resolved issues.

Network module

  • Fixed a networkagent crash on Windows that occurred when initialization failed. (OA-45935)
  • Improved interface sniffing stop conditions for Network Agent: after an "Interface was removed" system error for a specific interface, the Network Agent stops sniffing on that interface. (OA-45890)

Go

  • Fixed issue where OneAgent injects into unsupported 32-bit Go applications. (OA-46178)

AI causation engine

  • Query parameters of a URL are now correctly taken into account by the URL-based sampling mechanism. (OA-46472)

Extensions framework

  • Resolved an issue with loading MIB module when the filename was different from the module name itself. (DAQ-7376)

General

  • Fixed an issue with NGINX where enabing BizEvents feature caused `content-length` header to be stripped and `transfer-encoding: chunked` header to be added instead. (OA-47489)
  • On AIX, the missing disk I/O values (`bytesRead` and `bytesWritten`) are fixed by using the correct disk device name for standard disk device detection, which is the base for I/O data retrieval. (OA-47906)
  • Fixed an issue with PHP and Python modules not correctly loading URL-based sampling rules on startup. (OA-45635)
  • Fixed an issue in which the bizevent contenttype UI configuration was not passed correctly to NGINX worker processes, so the workers could not capture content when the contenttype was not the default. (OA-46187)

Live Debugger

  • Fixed an issue in the Node.js Live Debugger where, in certain cases, breakpoints might not have been properly added or removed. This could potentially lead to increased memory usage over time. (OA-47709)

Mainframe

  • Removed the "Loading collector peer list..." and "X entries loaded" log entries, which were leftovers from AppMon. (OA-46124)

Node.js

  • Fixed an issue in which using `--loader` in Node.js v18 or later caused OneAgent to crash. (OA-43190)
  • Disabled instrumentation for Node Redis version 5 and later, which is not supported at the moment. (OA-47247)

OS module

  • Fixed handling systemd services containing dots in their names on Linux. (OA-47556)
  • Fixed an issue with adding new rules for disk exclusions during runtime in Windows. (OA-45040)
  • Unused binaries from the 32- and 64-bitness directories (`dynatrace\oneagent\bin`) are removed even if the host has monitoring disabled. Aging on `any` folder is performed only if OneAgent is active. (OA-46325)
  • Fixed an issue with processing network metrics by the OneAgent OS module, in which the metrics update cycle could take a long time to complete, leading to gaps in the reported metrics, or to agent freeze and restart. (OA-47210)

OneAgent Installer

  • Fixed monitoring mode configuration changing from infra-only to full-stack on OneAgent upgrade from version 1.311. Customers who did not install OneAgent from scratch since 1.271 or did not use `--set-infra-only` (now deprecated) or `--set-monitoring-mode` options are affected. (OA-47690)

Webserver core

  • Fixed a special case where the whole body could not be captured when it was just a single byte. (OA-45298)

PHP

  • Fixed an issue with a OneAgent companion process that (for multi-process agent setups found, for example, in Apache, NGINX, and PHP applications on Linux) handles data communication to the Dynatrace cluster. Upon a crash and recreation by a watchdog, the companion process failed to initialize. This did not affect the application, but did affect data exchange to the Dynatrace cluster and, with that, led to missing monitoring data. (OA-46193)

Apache

  • Fixed an error that caused improper capture of request and response bodies and headers for Business Events when internal redirects in Apache Server occur. (OA-45164)

OneAgent for Android

General Availability (Build 8.315.1)

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

OneAgent for iOS

General Availability (Build 8.315.1)

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

OneAgent for JavaScript

General Availability (Build 1.315.1)

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