OneAgent release notes version 1.283

Rollout start: Jan 30, 2024

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

Support level
Oldest version supported
Standard Support
1.265
Enterprise Success and Support
1.259

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

Breaking changes

Ingest of container logs via OneAgent

Warning Breaking change Infrastructure Observability | Log Monitoring

Logs collected via OneAgent from Kubernetes container orchestration systems and non-orchestrated Docker environments are now reported with log.source set to Container Output instead of a path to the physical file they were ingested from.

This change allows for better aggregation of log sources displayed on various unified analysis pages and thus more intuitive navigation from them into Logs and events / Log explorer pages for more detailed analysis.

However, log ingest rules for Kubernetes and Docker logs are typically based on specific container-related attributes such as Kubernetes namespace or Container name.

Update: Using the log.source matcher to control containerized application logs' ingestion is now deprecated.

  • Such configurations are still temporarily valid but will require migration to using Kubernetes-related attributes instead of the log.source attribute in the near future.
  • A similar migration to account for changes in the log.source attribute for containers is required in log processing rules, but also in log metrics and log events configurations.

Removed default values of dt_security_context

Warning Breaking change Infrastructure Observability | Hosts

The permission field dt.security_context in the dt_host_metadata file is reserved for user-defined values only. It no longer has a default value if no values are explicitly specified by the user.

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

New technology support

For more information, see New technology support.

  • MongoDB 1.3 - 1.13 (Go module). OneAgent feature: Go MongoDB
  • OpenResty 25.3.1 (NGINX module)
  • z/OS 3.1 (zDC module)

End of support

For more information, see End of support announcements.

  • Node.js 19 (Node.js module)
    • Vendor end of support: 2023-06-01

New features and enhancements

Excluded Microsoft KM-TEST Loopback Adapter from detected NICs

Infrastructure Observability | Hosts

The Microsoft KM-TEST Loopback Adapter is excluded from detection and not reported to Dynatrace.

Resolved issues

General Availability (Build 1.283.139)

The 1.283 GA release contains 2 resolved issues.

Component
Resolved issues
1
1

General

  • To limit the impact of breaking change "Ingest of container logs via OneAgent": Using the `log.source` matcher to control containerized application logs' ingestion is now deprecated. Such configurations are still temporarily valid, but will require migration to using Kubernetes-related attributes instead of the `log.source` attribute in the near future. A similar migration to account for changes in the `log.source` attribute for containers is required in log processing rules. (LOG-6337)

.NET

  • Fixed an issue in the WCF v2 feature that resulted in duplicate service calls for the same request. (OA-26731)

Update 154 (Build 1.283.154)

This cumulative update contains 13 resolved issues and all previously released updates for the 1.283 release.

Component
Resolved issues
3
3
1
2
1
1
2

General

  • To limit the impact of breaking change "Ingest of container logs via OneAgent": Using the `log.source` matcher to control containerized application logs' ingestion is now deprecated. Such configurations are still temporarily valid, but will require migration to using Kubernetes-related attributes instead of the `log.source` attribute in the near future. A similar migration to account for changes in the `log.source` attribute for containers is required in log processing rules. (LOG-6337)
  • Corrected behavior in corner cases for configured async methods as a .NET messaging service. (OA-26098)
  • Fixed (removed) overly verbose log entries for PHP that had resulted in a high number of WorkProxy-related entries that could not be turned off. (OA-26856)

Java

  • Dynatrace data enriched in unstructured Logback logs is now enclosed with `[!dt ]` bracketing. (OA-25931)
  • Fixed an issue that sometimes caused a OneAgent crash if an application threw a `StackOverflowError` during startup. (OA-27310)
  • Fixed an issue that sometimes caused a OneAgent crash if an application threw a `StackOverflowError` during startup. (OA-27310)

Mainframe

  • Fixed a SQL Fetch (CLI0125E) Function sequence error. (OA-26727)

OS module

  • Fixed an issue that caused extensions to not run on Azure servers. (HOST-5182)
  • Fixed an issue that caused extensions to not run on Azure servers. (HOST-5182)

Apache

  • Fixed rebranded Apache Web Server (IHS) crash issue by disabling Apache Log Enrichment functionality for such servers by default. (OA-29400)

OpenTracing module

  • Added support for Envoy 1.29.x. (OA-26499)

.NET

  • Fixed an issue where requests to the RUM beacon URL were allowed to affect the application availability under certain conditions. (OA-29185)
  • Fixed an issue in the WCF v2 feature that resulted in duplicate service calls for the same request. (OA-26731)

OneAgent for Android

OneAgent for Android updates

Digital Experience | RUM Mobile

  • A new variant of the stopWebRequestTiming API method was added to the OneAgent SDK for Android. Use the new stopWebRequestTiming(URI requestUri, int respCode, String respPhrase, long requestSize, long responseSize) API method to additionally pass the request and response sizes when reporting a web request. This additionally specified information will be then shown in the Dynatrace web UI on the following pages.
    • On the web requests details page (accessible via the Top providers section)—only request size is shown
    • On the User action analysis page for web requests attached to user actions—both request and response sizes are shown

    OneAgent for iOS

    Button and Menu initializers

    Digital Experience | RUM Mobile

    Added instrumentation for the iOS 17 Button and Menu initializers.

    Resolved issues

    General Availability (Build 8.283.1)

    The 8.283 GA release contains 2 resolved issues.

    OneAgent for iOS

    • SwiftUI instrumentor: constant binding variables are now instrumented correctly. (RUM-17172)
    • SwiftUI instrumentor: control names with implicit constant references now resolve correctly. (RUM-17176)

    OneAgent for JavaScript resolved issues

    General Availability (Build 1.283.3)

    The 1.283 GA release contains 1 resolved issue.

    JavaScript

    • Fixed an issue where the XHR module instantiated progress events as `Event` instead of `ProgressEvent`, which made `instanceof` checks fail. This was especially an issue with the XHR wrapper Flutter uses. (RUM-17230)