OneAgent release notes version 1.303

Rollout start: Nov 5, 2024

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

Support level
Oldest supported version
1.285
1.279

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

Breaking changes

Extensions 1.0 framework end of life

OneAgent 1.299 is the last version supporting OneAgent Extensions 1.0 framework. You can continue using OneAgent Extensions 1.0 if you stay at OneAgent version 1.299. Note that this means you'll be using an unsupported Python version 3.8. We strongly recommend migrating your extensions to the latest Extensions 2.0 framework.

For environments with Extensions 1.0, the OneAgent version 1.301 rollout starts after Oct 31, 2024.

For more information, see General guidance and how to migrate.

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.

End of support

For more information, see End of support announcements.

New features and enhancements

Log agent security rules have been relaxed

Infrastructure Observability | Log Monitoring

The log agent security rules have been relaxed to allow greater flexibility in log file handling. This change supports a broader range of use cases, as described below:

  • Each include rule now adds an optional rotation suffix ([-._]*) at the end of the filename. This means filenames can have suffixes for rotation without requiring explicit configuration.
  • Log files are now permitted within a log or logs subdirectory at any directory level. Subdirectory names are now more flexible, allowing variations such as logfile, logfiles, and applogs.
  • The previous block on files in the /usr/ directory is lifted, provided the standard log directory or extension conditions are met.
  • Log files with a .txt extension are now allowed, broadening compatibility for text-based log formats.

These changes don't impact the rules for autodetection of log files, which remain the same.

OS Services events enrichment

Infrastructure Observability | Hosts

Events generated by OS Services settings will now be enriched with the dt.settings.object_id member used to identify settings used to raise an event uniquely.

Java module automatically traces incoming Kafka messages based on @KafkaListener annotation

Infrastructure Observability | Hosts

The OneAgent Java module now automatically traces incoming Kafka messages if an application uses a meta-annotation using Spring's @KafkaListener annotation.

Automatic log enrichment if JMX remote is enabled

Infrastructure Observability | Hosts

The OneAgent Java module now automatically enriches loglines if an application uses SLF4J, JMX remote is enabled, and the JUL LogManager is active.

Apache subrequests handling improved

Infrastructure Observability | Hosts

Apache subrequests (including mod_dir usage) are now properly handled, preventing potential OneAgent crashes.

VxFS support added

Infrastructure Observability | Hosts

We have added support for disks using the VERITAS File System (VxFS).

Infrastructure event enrichment

Infrastructure Observability | Hosts

Events generated by infrastructure settings will now be enriched with the dt.settings.object_id member, which identifies settings used to raise an event uniquely.

DiskEdge event enrichment

Infrastructure Observability | Hosts

Events generated by Disk Edge settings will now be enriched with the dt.settings.object_id member, which identifies settings used to raise an event uniquely.

Optimized log processing in OneAgent

Infrastructure Observability | Hosts

Log processing in OneAgent has been optimized to significantly reduce both memory and CPU usage.

Resolved issues

General Availability (Build 1.303.42)

The 1.303 GA release contains 13 resolved issues.

Component
Resolved issues
2
1
3
1
1
3
2

.NET

  • Reduced overhead of OneAgent CLV/RAP features for .NET applications. (OA-37810)
  • Improved stability of OneAgent CLV/RAP features for .NET applications. (OA-37813)

AI causation engine

  • Resolved issue in which, when a valid traceparent tag was processed without any additional Dynatrace tag information, root paths weren’t sampled. (OA-37321)

General

  • Fixed the problem that the `dt.host_group.id` dimension contained the `dt.entity.host_group` dimension and vice versa. (OA-37524)
  • OS services are cleared after 3 failed attempts to create an sdbus handle, which previously caused outdated data about OS services. (OA-35297)
  • Fixed an issue in which, when OneAgent was executed in Google Cloud Run with the execution environment in the first version, memory usage metrics relevant to billing could not be sent. (OA-37856)

Live Debugger

  • Live Debugger will now iterate the full list of ActiveGates. (OA-35805)

Mainframe

  • Fixed an issue in which the zRemote unregistered a mainframe component unexpectedly in certain conditions. (OA-38261)

Network module

  • Fixed calculation of the size of TCP data segment in case of TCP offloading. (OA-37005)
  • Fixed calculation of timeouts and time durations that could result in inflated retransmission metrics. (OA-35217)
  • Fixed a oneagentnetwork crash related to NIC state change from down to up. (OA-37724)

OS module

  • Fixed incorrect "restart required" warning displayed for some Apache HTTPD with PHP deployments. (OA-37247)
  • Fixed a rare case where a connectivity problem could have been raised with connectivity alerting disabled for a particular process group. (HOST-6683)

OneAgent for Android

General Availability (Build 8.303.1)

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

OneAgent for iOS

General Availability (Build 8.303.1)

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

OneAgent for JavaScript

General Availability (Build 1.303.1)

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