OneAgent release notes version 1.231

Rollout starts January 10, 2022

New analytics capabilities for messaging system-related anomalies
Business transactions depend on the performance of applications. In modern applications built with microservices, decoupled services are common, and events are used to communicate between services, making it important for DevOps teams to have full observability into the performance of messaging systems.
Automatic connection of logs and traces accelerates AI-driven cloud analytics
As digital transformation continues to accelerate and enterprises modernize with the adoption of cloud-native architectures, the number of interconnected components and microservices is exploding. Logs are a critical ingredient in managing and optimizing these application environments. Dynatrace now unifies log monitoring with its patented PurePath technology for distributed tracing and code-level analysis. Logs are now automatically connected to distributed traces for faster analysis and optimization of cloud-native and hybrid applications.

With this release, the oldest supported OneAgent versions are:

Dynatrace ONE	Dynatrace ONE Premium
1.213	1.207

Dynatrace extension framework upgrade notice

Starting with Dynatrace OneAgent and ActiveGate version 1.231, we are upgrading the Extension Framework (also referred to as the plugins framework) from Python 3.6 to Python 3.8.

Consequences: Some Dynatrace extensions running in your environment may stop working and require redeployment of a new version prepared for Python 3.8.
Symptoms:
- No data is provided for affected metrics on dashboards, alerts, and custom device pages populated by the affected extension metrics.
- Extension logs display errors. Most often this will manifest itself as Python ModuleNotFoundError in the PluginAgent log.
- Sometimes the Python virtual machine crashes.
Impact: This issue affects only those extensions that use native libraries called from Python code distributed with the extension.

Extension-specific advisory

Extension	What to do
Citrix Virtual Apps and Desktops IBM DataPower IBM DB2 LUW IBM i IBM MQ Juniper Networks Microsoft SQL Server (MSSQL - remote monitoring) SAP HANA Database	In the Dynatrace menu, go to Hub. Find and select one of the extensions listed to the left. On the extension details page, select Download to download the extension ZIP file to your machine. If there are operating system options, be sure to select the correct download for your deployment. Deploy the extension per the instructions on the corresponding documentation page. (In the list to the left, select the name of the extension.) For assistance, please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
All out-of-the-box built-in extensions	No action required. Extensions distributed with OneAgent will be updated automatically to work with Python 3.8 together with the Python upgrade.
Custom extensions	To learn about upgrading custom Dynatrace extensions from Python 3.6 to Python 3.8, see Upgrade custom Dynatrace extensions from Python 3.6 to Python 3.8.

Extension

What to do

In the Dynatrace menu, go to Hub.
Find and select one of the extensions listed to the left.
On the extension details page, select Download to download the extension ZIP file to your machine. If there are operating system options, be sure to select the correct download for your deployment.
Deploy the extension per the instructions on the corresponding documentation page. (In the list to the left, select the name of the extension.)

For assistance, please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

All out-of-the-box built-in extensions

No action required. Extensions distributed with OneAgent will be updated automatically to work with Python 3.8 together with the Python upgrade.

Custom extensions

To learn about upgrading custom Dynatrace extensions from Python 3.6 to Python 3.8, see Upgrade custom Dynatrace extensions from Python 3.6 to Python 3.8.

Java

Added support for Log4J2 (Apache) 2.7.x - 2.12.x

Go

Added support for Logrus 1.5 - 1.8
Added support for Zap 1.10 - 1.20

Operating systems

Future Dynatrace OneAgent operating systems support changes

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

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

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

UNIX: IBM AIX 7.2 TL3
- POWER8, POWER9
- 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 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

Past Dynatrace OneAgent technology support changes

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

OpenTelemetry 0.16.0, 0.17.0 for Go

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

OpenTelemetry 0.18.0 for Go

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

OpenTelemetry 0.19.0 for Go

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

Past Dynatrace OneAgent operating systems support changes

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

Linux: Red Hat Enterprise Linux CoreOS 4.3
- x86-64
- Last compatible version: 1.213
UNIX: IBM AIX 7.2 TL2
- POWER8, POWER9
- Vendor announcement
- Last compatible version: 1.213

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

Linux: CentOS 6.x
- x86-64
- Vendor announcement
- Last compatible version: 1.215
Linux: Fedora 31
- x86-64
- Vendor announcement
- Last compatible version: 1.215
Windows: Windows Desktop 1803
- x86-64
- Vendor announcement
- Last compatible version: 1.215

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

Windows: Windows Desktop 1903
- x86-64
- Vendor announcement
- Last compatible version: 1.217
Windows: Windows Server 1903
- x86-64
- Vendor announcement
- Last compatible version: 1.217

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: Google Container-Optimized OS 77 LTS
- x86-64
- Vendor announcement
- Last compatible version: 1.217

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

Resolved issues

General Availability (Build 1.231.237)

General Availability (Build 1.231.237)

The 1.231 GA release contains 21 resolved issues.

Component	Resolved issues
Infrastructure Monitoring	6
Java	2
.NET	1
PHP	2
AI causation engine	1
All modules	2
General	1
OS module	4
Go	1
Plugin module	1

Infrastructure Monitoring

Extensions SFM status logs timestamps now match status metrics timestamps. (APM-327536)
Extension Execution Controller (EEC) no longer detects datasource timeout and fails to restart the process properly after CPU and memory saturation. (APM-330530)
To open a StatsD listening port in local StatsD ingest mode (OneAgent), a socket is now opened on `127.0.0.1:18125` (IPv4) if IPv4 is available, or on `[::1]:18125` (IPv6) if IPv4 is disabled. (APM-330474)
Extension Execution Controller (EEC) properly resolves extension version when minor patch version is not provided. (APM-328456)
Corrected CPU usage calculation method on Windows platform; resolves issue with occasional Extension Execution Controller (EEC) restart. (APM-327062)
Fixed a problem with manually setting the host group in standalone environments. (APM-338489)

Java

Incoming Web Request nodes created with the OneAgent SDK for Java are no longer shown as flawed if there is no HTTP Host header or a full URL provided. (ONE-66636)
ClassNotFoundException no longer occurs when log enrichment is enabled for Log4j. (ONE-67851)

.NET

Resolved a SecurityException in AspNetCore when monitoring exceptions that generated a `Methods must be security critical or security safe-critical to call native code.` log entry. (ONE-67782)

PHP

Resolved issue with OneAgent PHP module that broke headers in outgoing requests. (ONE-68614)
OneAgent PHP module no longer crashes when instrumenting method with return value capture. (ONE-67997)

AI causation engine

Custom tag information is now encoded in outgoing Dynatrace tags when tracecontext is enabled, resolving possible unstitched PurePaths. (ONE-67493)

All modules

The `--graph` and `--data-root` dockerd arguments for collecting Docker container metadata are now handled correctly. (ONE-66941)
Crash alert generation no longer leads to disk exhaustion when OneAgent is running in limited privileges mode. (ONE-66720)

General

IIS modules are now displayed correctly in web UI when IIS Insights is enabled. (APM-336632)

OS module

Child SAP processes are grouped to parent and are no longer visible as separate processes. (APM-337097)
Added support for Docker daemon userns-remap runtime option. (APM-340743)
Crash reports are now also aged when OneAgent is deactivated. (APM-327184)
Generating OSI ID treats the `set-host-id-source` parameter from the `deployment.conf` file as most important. On Azure and EC2, UUID or instance ID will be used only when `set-host-id-source` is set to `auto`. (APM-335475)

Go

OneAgent is now injected correctly into statistically linked Go binaries started via `execv()` or `execvp()` calls. (ONE-68208)

Plugin module

Initialization query for MS SQL counters now handles server restarts correctly. (APM-328369)