ActiveGate release notes version 1.301

Pre-release information

This is an ongoing summary of changes in this planned release. Check back here at GA for the final version.

Rollout start: Oct 8, 2024 (planned)

For environments with Extensions 1.0, rollout starts after Oct 31, 2024. See End of life announcement.

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

Support level
Oldest supported version

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

Breaking changes

Extensions 1.0 framework end of life

ActiveGate 1.299 is the last version supporting Extensions 1.0 framework. You can continue using ActiveGate Extensions 1.0 if you stay at ActiveGate 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 ActiveGate 1.301 rollout starts after Oct 31, 2024.

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

Announcements

End of support for private Synthetic locations on Red Hat/CentOS 7

Chromium development for Red Hat/CentOS 7 stopped at version 126. For important security and stability reasons, we've decided to discontinue our support for installing Synthetic-enabled ActiveGate on Red Hat/CentOS 7 after ActiveGate version 1.305. ActiveGate version 1.305 will be the last Synthetic-enabled ActiveGate supported on Red Hat/CentOS 7. Additionally, with Dynatrace version 1.306, we will introduce mechanisms preventing Synthetic-enabled ActiveGates on Red Hat/CentOS 7 from being updated beyond version 1.305.

  • Since RHEL7 reached End of Maintenance support on June 30th 2024, all it's packages have been archived. This means that it may not be possible to find the required dependencies for update.

Log attribute becomes a content-like field

Infrastructure Observability | Logs

Starting with Cluster and Environment ActiveGate version 1.303, the log attribute will be treated in a similar way as content, message, payload and body attribute. These attributes are considered a content attribute of the log message.

Action might be required: If there is no content attribute defined for a given log source, the log attribute will be treated as content. If you have any log processing, log metric, and/or log events rules set on the log attribute, you'll need to update your configuration.

The change will ensure data ingested in through the log attribute that exeeds 2.5KB isn't trimmed and will be accepted up to 256KB, which is the default content attribute limit in OpenPipeline. For classic log processing pipeline ingestion, the limits are 250B for any log atribute and 64kB for content.

New features and enhancements

Amazon Linux 2023 for Synthetic-enabled ActiveGate

Digital Experience | Synthetic

The following operating system is now supported for Synthetic-enabled ActiveGate:

  • Amazon Linux 2023 (uses Chrome for Testing)

IPv6 support for Network Availability Monitors

Digital Experience | Synthetic

ActiveGate version 1.301+ Dynatrace version 1.302+

NAM has been improved by adding support for IPv6. Now, you can use NAM to check network and device availability in IPv6 networks.

Operating system support

    Future Dynatrace ActiveGate 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 June 2025

    Past Dynatrace ActiveGate 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 June 2024
    The following operating systems are no longer supported since 01 July 2024

    Resolved issues

    General Availability (Build 1.301.2)

    The 1.301 GA release contains 1 resolved issue.

    ActiveGate

    • Improved reconnection mechanism to resolve rare cases related to Cluster update where ActiveGate was unable to reconnect. (DMX-8033)