OneAgent release notes version 1.303

Latest Dynatrace
Release notes

Rollout start: Nov 5, 2024

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

Support level	Oldest supported version
Standard Support	1.285
Enterprise Success and Support	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

Technology support version schema

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.