OneAgent release notes version 1.209

Rollout start: Feb 10, 2021

With this release, the oldest supported OneAgent versions are:

Standard Support

Enterprise Success and Support

1.191

1.185

Windows installer

We deprecate the no_create installation parameter starting with OneAgent version 1.209. The parameter disabled user creation when installing OneAgent. Starting with version 1.209, when you use the no_create parameter, the OneAgent installer applies the LocalSystem parameter without any warning. The no_create setting isn't converted to LocalSystem for existing installations when running an update. For more information, see OneAgent extension user.

Deprecating installation parameters

Starting with OneAgent version 1.213, the following deprecated installation parameters will be removed.

Deprecated parameters
New --set-param=<value> parameter
SERVER
--set-server
TENANT
--set-tenant
TENANT_TOKEN
--set-tenant-token
PROXY
--set-proxy
HOST_GROUP
--set-host-group
APP_LOG_CONTENT_ACCESS
--set-app-log-content-access
DISABLE_SYSTEM_LOGS_ACCESS
--set-system-logs-access-enabled
INFRA_ONLY
--set-infra-only

If you use any of these parameters for your OneAgent deployment, please be sure to replace them with the corresponding --set-param=<value> parameters.

For more information, see

.NET Framework

.NET and .NET Core

z/OS

Current Dynatrace OneAgent technology support changes

Dynatrace OneAgent 1.209 is the last version to support the following technologies
  • OpenTelemetry 0.13.0 for Go

Current Dynatrace OneAgent operating systems support changes

The following operating systems will no longer be supported starting 01 February 2021

Future Dynatrace OneAgent technology support changes

Dynatrace OneAgent 1.213 will be the last version to support the following technologies
  • OpenTelemetry 0.16.0, 0.17.0 for Go
Dynatrace OneAgent 1.215 will be the last version to support the following technologies
  • OpenTelemetry 0.18.0 for Go
Dynatrace OneAgent 1.217 will be the last version to support the following technologies
  • OpenTelemetry 0.19.0 for Go
Dynatrace OneAgent 1.221 will be the last version to support the following technologies
  • OpenTelemetry 0.20.0 for Go
  • OpenTelemetry 0.18, 1.0.0-rc.0, 1.0.0-rc.3 for Node.js
Dynatrace OneAgent 1.227 will be the last version to support the following technologies
  • OpenTelemetry 1.0.0-RC1 for Go
  • OpenTelemetry 1.0.0-RC2 for Go

Future Dynatrace OneAgent operating systems support changes

The following operating systems will no longer be supported starting 01 December 2024
The following operating systems will no longer be supported starting 01 January 2025
The following operating systems will no longer be supported starting 01 April 2025
The following operating systems will no longer be supported starting 01 May 2025
The following operating systems will no longer be supported starting 01 June 2025
The following operating systems will no longer be supported starting 01 July 2025

Past Dynatrace OneAgent operating systems support changes

The following operating systems are no longer supported since 01 May 2024
The following operating systems are no longer supported since 01 July 2024
The following operating systems are no longer supported since 01 November 2024

Resolved issues

General Availability (Build 1.209.130)

The 1.209 GA release contains 33 resolved issues (including 1 vulnerability resolution).

All modules

  • Corrected detection of Apache command line arguments without a space between the switch ("-d" or "-f") and the path. (ONE-52325)
  • Enabled using OneAgent AIX kernel extension on systems also running Symantec Data Center Security. (ONE-53112)
  • Resolved issue causing truncation of very long Java class names. (ONE-49537)
  • Resolved potential OneAgent crash when the `correlation.enableServerIdLogicForTraceId` flag is enabled and cluster runtime configuration initially provides an empty server list. (ONE-52929)

General

  • Vulnerability: Connection-specific OneAgent options for the Java code module are no longer passed via JVM arguments. (APM-267817)
  • Container injection now supports Docker daemons that have the "userns-remap" option enabled. (APM-276651)
  • InnoDB buffer pool data chart now uses correct unit. (APM-272628)
  • Fixed calculation of Disk Utilization Time metric on Linux. (APM-271942)

Mainframe

  • Resolved zRemote's inability to allow a ZDC reconnect after a disconnect due to latency errors. (ONE-52827)
  • Resolved zDC inability to reconnect to zRemote after a disconnect. (ONE-52495)
  • Resolved load issues with the zRemote due to insufficient buffering. (ONE-52006)

OS module

  • Improved detection of .NET Core version. (ONE-51764)
  • Fixed incorrect grouping of some Citrix Xen processes as Citrix VDA. (ONE-50287)
  • Resolved issue in which CRI-O container metrics may have container ID instead of container name as dimension. (ONE-50207)
  • Added recognition of Windows Server 20H2. (APM-269100)
  • Resolved issue in which OneAgent Linux module would stop monitoring for about 20 minutes. (APM-277455)
  • Reduced amount of data sent to cluster when monitoring of Windows Services is active. (ONE-53777)
  • Fixed issue with getting information about Oracle SID when two SIDs on hosts are similar to each other. (APM-274962)

OneAgent Installer

  • Extended OneAgent SELinux module with a rule allowing lnk_file read access to oneagent_log_t. (APM-274758)
  • OneAgent SELinux module now includes rules allowing for containerized GO applications to be instrumented. (APM-274692)
  • DISABLE_ROOT_FALLBACK value is no longer incorrectly inverted when applying the setting. (APM-274564)
  • Installer pass-through logic now correctly handles parameters with spaces. (APM-274654)
  • Fixed issue with recursive bind mounts missing in OneAgent container. (APM-266435)
  • Console windows no longer flash during interactive installation on Windows. (APM-271080)
  • The values of --set-tenant-token and --set-proxy no longer appear in installer log. (APM-273192)
  • Installer now correctly refuses to deploy on Windows 7. (APM-274660)

ActiveGate

  • Auto-update process now stops Synthetic service before updating Synthetic package. (APM-269619)

.NET

  • Fixed an issue in which the OneAgent .NET code module could not be successfully initialized when the legacy AppMon profiler GUID was set. (ONE-52294)

PHP

  • Fixed issues during result statistics collection in OneAgent PHP module SQL Server sensor. (ONE-52341)
  • Resolved a memory freeing issue when cleaning up MySQLi sensor metadata on request end. (ONE-53440)

Go

  • Provided workaround for Go processes built with Go 1.14 or higher, which may become unresponsive on high load. (ONE-52482)

NGINX

  • Improved detection of NGINX ngx_http_proxy_connect_module. (ONE-51258)

Watchdog

  • Resolved issue with Watchdog not using exponential backoff when restarting observed binaries. (APM-273932)

Update 148 (Build 1.209.148)

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

Component
Resolved issues

All modules

  • Enabled using OneAgent AIX kernel extension on systems also running Symantec Data Center Security. (ONE-53112)

General

  • Resolved issue that made OneAgent OS module process leave defunct child processes. (APM-279814)

.NET

  • Resolved tagging issues in OneAgent .NET code module. (ONE-53228)

Update 154 (Build 1.209.154)

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

Go

  • Resolved issue with missing Go metrics when using external metadata. (ONE-54663)

Update 163 (Build 1.209.163)

This cumulative update contains 4 resolved issues and all previously released updates for the 1.209 release.

Component
Resolved issues

Mainframe

  • Resolved issue with process group naming rules for CICS and IMS. They’re now available for process group naming. (ONE-54770)

.NET

  • Improved configuration handling of the OneAgent .NET code module for MSMQ, IBM MQ, Azure Service Bus, and RabbitMQ sensor v2. (ONE-54907)

IIB

  • When an HTTPRequest fails with a request URL that is overwritten at runtime (e.g., via preceding Compute node), the overwritten request URL is now considered as the correct destination. (Previously, only the static URL property of the HTTPRequest node was taken into account as the destination; runtime overwrites were ignored.). (ONE-54682)

AI causation engine

  • Resolved an issue in an internal API call that led to incorrect count of attachment usage for paths longer then 10,000 nodes (truncated paths), which prohibited the start of new paths and prevented monitoring. (ONE-54897)

Update 170 (Build 1.209.170)

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

Component
Resolved issues

Java

  • Resolved issue in which webMethods Integration Server threw a ClassCastException after upgrade to OneAgent version 209. (ONE-54963)

.NET

  • Improved configuration handling of the OneAgent .NET code module for MSMQ, IBM MQ, Azure Service Bus, and RabbitMQ sensor v2. (ONE-54907)

AI causation engine

  • Resolved an issue in an internal API call that led to incorrect count of attachment usage for paths longer then 10,000 nodes (truncated paths), which prohibited the start of new paths and prevented monitoring. (ONE-54897)

OneAgent for mobile resolved issues

General Availability (Build .209)

The .209 GA release contains 6 resolved issues.

Mobile

  • OneAgent for iOS: improved Session Replay related logging. (ONE-45812)
  • OneAgent for iOS: reportError with NSException sometimes had missing exception name. (ONE-50560)
  • OneAgent for iOS: improved UIWindowScene timings. (ONE-51153)
  • Android Agent: Improved duration measurement for empty user actions. (ONE-51649)
  • Symbolication Client: Improved bundle name parsing. (ONE-52535)
  • OneAgent for iOS: fixed crash on fetching cookie domains in hybrid applications. (ONE-53411)