ActiveGate release notes version 1.303

Rollout start: Nov 5, 2024

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

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. We plan to have ActiveGate version 1.305 as the last Synthetic-enabled ActiveGate supported on Red Hat/CentOS 7. Additionally, with Dynatrace version 1.306, we plan to introduce mechanisms preventing Synthetic-enabled ActiveGates on Red Hat/CentOS 7 from being updated beyond version 1.305.

End of support for private Synthetic locations on Amazon Linux 2

Chromium development for Amazon Linux 2 stopped at version 126. For important security and stability reasons, we've decided to discontinue our support for installing Synthetic-enabled ActiveGate on Amazon Linux 2 after ActiveGate version 1.307. We plan to have ActiveGate version 1.307 as the last Synthetic-enabled ActiveGate supported on Amazon Linux 2. Additionally, with Dynatrace version 1.308, we plan to introduce mechanisms preventing Synthetic-enabled ActiveGates on Amazon Linux 2 from being updated beyond version 1.307.

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 to the content, message, payload, and body attributes. 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.

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

New features and enhancements

Chromium support for private Synthetic locations

Digital Experience | Synthetic Monitoring

Chromium 126 is the latest supported version for Synthetic-enabled ActiveGate installed on:

Chromium 129 is the latest supported version for Synthetic-enabled ActiveGate installed on:

Chromium 129 is bundled with the Windows ActiveGate installer.

For more information on supported and provided Chromium versions, see Requirements for private Synthetic locations and Create a private Synthetic location.

Operating system support

Resolved issues