OneAgent release notes version 1.239

Rollout starts April 27, 2022

With this release, the oldest supported OneAgent versions are:

Java

• Added support for OpenTelemetry agent 1.12

z/OS

• oneagentzos-R12390.pax is now available

.Net Core

• Added automatic Real User Monitoring (RUM) injection for ASP.NET Core applications running on a Kestrel web server. To enable this as a OneAgent feature
  1. In the Dynatrace menu, go to Settings > Server-side service monitoring > Deep monitoring.
  2. Expand the New OneAgent features section, find Enable Real User Monitoring (RUM) for ASP.NET Core, and turn it on.

Go

• Added support for Go 1.18

New features and enhancements

Installer

On Windows, usage of legacy dtuser will be implicitly converted to Local System account during update.

Log Monitoring

The OneAgent log module is able to extract attributes from log content and enrich log records. The OneAgent log module now processes the enriched log data, improving performance. For details, see Connecting log data to traces.

OneAgent watchdog

Two new parameters were introduced (currently used only in OneAgent Linux installation):

• coredump.non_root_use_sigquit

  If set and watchdog is started with a non-root user (uid != 0), watchdog sends SIGQUIT signal to child process in case of ping timeout, memory exceeded, or shutdown timeout to trigger a core dump. Default: false

• non_root_drop_capabilities

  If set and watchdog is started with a non-root user (uid != 0), watchdog drops all capabilities after initialization (before starting any child processes) and marks its own process as dumpable (prctl(PR_SET_DUMPABLE, 1)). Default: false

Operating systems

• Added support for CentOS Stream 9
• Added support for IBM AIX 7.3 TL0

Current Dynatrace OneAgent technology support changes

Dynatrace OneAgent 1.239 is the last version to support the following technologies

• JBoss Application Server 6, 7 for Java
  • The vendor has de-supported this technology and version with 2009-09-01
• JBossWS (JBoss AS) 4.x for Java
  • The vendor has de-supported this technology and version with 2009-09-01
• OpenTelemetry 0.0.2 for PHP
• Node.js 8 for Node.js
  • The vendor has de-supported this technology and version with 2019-12-31

Future Dynatrace OneAgent operating systems support changes

The following operating systems will no longer be supported starting 01 June 2022

• Linux: Fedora 33
  • x86-64
  • Vendor announcement

The following operating systems will no longer be supported starting 01 July 2022

• Linux: CentOS 8.x
  • x86-64
  • Vendor announcement
• Linux: CentOS 8.x
  • PPCLE
  • Vendor announcement
• Linux: CentOS 8.x
  • ARM64 (AArch64)
  • Vendor announcement
• Linux: Google Container-Optimized OS 85 LTS
  • x86-64
  • Vendor announcement
• Linux: openSUSE 15.2
  • x86-64, PPCLE
  • Vendor announcement
• Windows: Windows Desktop 10 2004
  • x86-64
  • Vendor announcement
• Windows: Windows Server 2004
  • x86-64
  • Vendor announcement

The following operating systems will no longer be supported starting 01 August 2022

• Linux: Ubuntu 21.04
  • Vendor announcement

The following operating systems will no longer be supported starting 01 October 2022

• Linux: SUSE Linux Enterprise Server 11.4
  • Vendor announcement

The following operating systems will no longer be supported starting 01 November 2022

• Linux: Ubuntu 14.04 LTS
  • Vendor announcement

The following operating systems will no longer be supported starting 01 December 2022

• Linux: Fedora 34
  • x86-64
  • Vendor announcement
• Windows: Windows Desktop 10 1909
  • x86-64
  • Vendor announcement
• Windows: Windows Server 20H2
  • x86-64
  • Vendor announcement

The following operating systems will no longer be supported starting 01 January 2023

• Linux: Debian 8, 9
  • x86-64
  • Vendor announcement
• Linux: SUSE Linux Enterprise Server 12.3
  • Vendor announcement

Past Dynatrace OneAgent technology support changes

Dynatrace OneAgent 1.221 was the last version to support the following technologies

• OpenTelemetry 0.20.0 for Go
• OpenTelemetry 0.18.x, 1.0.0-rc.0, 1.0.0-rc.3 for Node.js

Dynatrace OneAgent 1.227 was the last version to support the following technologies

• OpenTelemetry 1.0.0-RC1 for Go
• OpenTelemetry 1.0.0-RC2 for Go

Dynatrace OneAgent 1.233 was the last version to support the following technologies

• Node.js 15 for Node.js
  • The vendor has de-supported this technology and version with 2021-06-01

Past Dynatrace OneAgent operating systems support changes

The following operating systems are no longer supported since 01 September 2021

• Linux: Red Hat Enterprise Linux CoreOS 4.4
  • x86-64
  • Last compatible version: 1.223
• Linux: openSUSE 15.1
  • x86-64, PPCLE
  • Vendor announcement
  • Last compatible version: 1.223

The following operating systems are no longer supported since 01 October 2021

• Linux: SUSE Linux Enterprise Server 12.2
  • Vendor announcement
  • Last compatible version: 1.225

The following operating systems are no longer supported since 01 December 2021

• Linux: Fedora 32
  • x86-64
  • Vendor announcement
  • Last compatible version: 1.227
• Windows: Windows Server 1909
  • x86-64
  • Vendor announcement
  • Last compatible version: 1.227

The following operating systems are no longer supported since 01 February 2022

• Linux: Red Hat Enterprise Linux CoreOS 4.5
  • x86-64
  • Last compatible version: 1.235
• Linux: Ubuntu 20.10
  • Vendor announcement
  • Last compatible version: 1.225

The following operating systems are no longer supported since 01 March 2022

• Linux: Google Container-Optimized OS 81 LTS
  • x86-64
  • Vendor announcement

The following operating systems are no longer supported since 01 April 2022

• UNIX: IBM AIX 7.2 TL3
  • POWER8, POWER9
  • Vendor announcement

Resolved issues

• General Availability (Build 1.239.196)
• Update 198 (Build 1.239.198)
• Update 205 (Build 1.239.205)
• Update 209 (Build 1.239.209)
• Update 216 (Build 1.239.216)
• Update 220 (Build 1.239.220)
• Update 226 (Build 1.239.226)

General Availability (Build 1.239.196)

The 1.239 GA release contains 10 resolved issues.

NGINX

• Renamed NGINX variables used for NGINX access.log enrichment to use a "dt_" prefix in order to avoid name conflicts with other modules. (ONE-72896)

All modules

• Corrected issue in which, in rare circumstances, incorrect values were assigned to Kubernetes properties such as pod name, container name, or namespace. (ONE-72282)

Cluster

• The datasource-java version has been backported to correct reverse DNS lookup. (APM-365066)

Infrastructure Monitoring

• Datasource now sends collected metrics more frequently to resolve an issue with gaps in charts. (APM-365736)
• Fixed rare issue where EEC would report incorrect extremely high CPU usage after restarting datasource due to high CPU. (APM-360930)
• StatsD data source now prints collected self-monitoring metrics to the log on process exit. (APM-360169)

Logging module

• Renamed config options responsible for severity detection to `LAConfigSeverityDetectionLimit_Bytes` and `LAConfigSeverityDetectionLinesLimit`. (APM-356991)

OS module

• OneAgent OS module now properly reports host memory metrics, even if CONFIG_VM_EVENT_COUNTERS is disabled in Linux kernel configuration. (APM-360172)

.NET

• Log enrichment for MS extension logging no longer leads to index-out-of-range exceptions, and correct prefixes are now used. (ONE-73433)

OneAgent Installer

• Resolved issue in which installer was stuck when trying to disable abrt-ccpp service that does not exist on SLES systems. (APM-362992)

Update 198 (Build 1.239.198)

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

Update 205 (Build 1.239.205)

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

PHP

• Fixed issue with getting multiple results from request attributes set for one function. (ONE-74577)

Update 209 (Build 1.239.209)

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

.NET

• Improved stability of the OneAgent .NET module in Infrastructure Mode. (ONE-74546)

IIB

• Added troubleshooting agent options to disable the writing Dynatrace trace tags for Java (via JavaCompute node) and .NET (via DotNetComputeNode) to folder "LocalEnvironment.Variables.Dynatrace", introduced in 1.229. (ONE-74722)

Update 216 (Build 1.239.216)

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

Update 220 (Build 1.239.220)

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

Update 226 (Build 1.239.226)

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

Mainframe

• Subagents are registered with zRemote version again. This fixes deactivation of the zAgent if an outdated subagent is trying to connect. (ONE-75119)

PHP

• Added additional data capturing when redis call method fails. (ONE-74172)

General

• Corrected handling of "Content-Encoding" header of compressed content generated by FCGI server, resolving issue in which OneAgent didn't inject JavaScript snippet to HTML page. (APM-367380)

OneAgent for mobile resolved issues

• General Availability (Build 1.239)

General Availability (Build 1.239)

The 1.239 GA release contains 5 resolved issues.

Mobile

• OneAgent for iOS: Improved static XCFramework support. (RUM-4317)

Mobile Agent

• OneAgent for iOS: Improved Swift Package Manager compatibility for static XCFramework. (RUM-4973)
• OneAgent for Android: Fixed issue that caused a crash when OneAgent was unable to determine display metrics. (RUM-4891)
• Session Replay for iOS: Fixed issue with starting the Session Replay module in certain scenarios. (RUM-5319)

Mobile Session Replay

• Session Replay for iOS: Fixed problem showing the debug frame highlight when debug masking was not also enabled. (ONE-73743)

OneAgent for JavaScript resolved issues

• General Availability (Build 1.239.128)

General Availability (Build 1.239.128)

The 1.239 GA release contains 1 resolved issue.

JavaScript

• Fixed an issue that occurred with the Proxy API XHR wrapper in late mode when another XHR wrapper was present as well. (RUM-5003)