ActiveGate release notes version 1.295

Rollout start: Jul 16, 2024

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

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

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.

New features and enhancements

Syslog ingestion

Infrastructure Observability | Logs

The new Syslog integration enables administrators to oversee and manage log files from various system components through Syslog.

Configure Environment ActiveGate on Linux to collect syslog logs from your network and ingest them into Dynatrace. The integration supports logs from network devices, Linux hosts, Syslog servers, and other Syslog producers.

For detailed instructions on how to enable Syslog ingestion, see Syslog ingestion with ActiveGate.

Improved management of ActiveGate SELinux file contexts

Infrastructure Observability | SELinux

ActiveGate removes and upgrades all file contexts defined for its SELinux module.

Upgrade to Java 17 and change garbage collector to G1

Infrastructure Observability | Java

In ActiveGate, Java has been upgraded from version 11 to version 17. With this upgrade, the garbage collector for the JVM has been changed from CMS (which is no longer available) to G1.

As a result, increased memory usage is expected behavior after ActiveGate update. This is strictly related to use of a different garbage collector mechanism. To achieve better performance, G1 is more likely to use more (or even all) memory granted to JVM to allocate the heap memory.

This shouldn’t have a negative impact on the ActiveGate in normal cases, since the ActiveGate should be running on a dedicated system.

You might need to reduce the maximum Java heap size from the default value in certain cases, such as if:

Added default ingest delay for some of Route53Resolver and NATGateway metrics

Infrastructure Observability | AWS

A default ingest delay for the following AWS metrics was added to improve data accuracy.

Log ingestion APIs rich types support

Infrastructure Observability | Log Monitoring

When ingesting logs into new OpenPipeline custom processing pipelines, the Log Monitoring API - POST ingest logs and OpenTelemetry logs ingest API support all JSON types. For other pipelines, all ingested log values continue to be converted to string type.

Chromium support for private Synthetic locations

Digital Experience | Synthetic Monitoring

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

Chromium 125 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