What's new in Dynatrace ActiveGate 1.345

• Release notes
• 4-min read
• Published Aug 12, 2026
• Rollout start on Aug 25, 2026

This page showcases new features, changes, and bug fixes in Dynatrace ActiveGate version 1.345. It contains:

Oldest supported versions

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

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

Feature updates

Application Observability

Watchdog: switch from TCP to named pipe

ActiveGate watchdog communication switches from TCP sockets to named pipes, aligning with OneAgent. This improves reliability and eliminates ping failures caused by TCP connection issues.

Digital Experience | Synthetic

Browser support for private Synthetic locations

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

Chrome for Testing 151 is the latest supported version for Synthetic-enabled ActiveGate installed on:

Chromium 151 is bundled with the Windows ActiveGate installer.

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

Infrastructure Observability | Extensions

Improved metric enrichment consistency in Extension Execution Controller

Extension Execution Controller (EEC) enrichment of outgoing metrics with additional context now complies with data formatting rules before it reaches Dynatrace. Normalization is applied without distinction across different types of enrichment data.

No configuration changes are needed on your part.

Infrastructure Observability | Kubernetes

Ingest enrichment support for custom rules

ActiveGate now supports ingest enrichment for custom rules. For details, see Enrich Kubernetes telemetry with primary Grail fields and tags.

Known limitations:

Infrastructure Observability | Kubernetes

Request and limit calculation improved

CPU, memory request, and limit metrics now account for pod-level resources introduced in Kubernetes version 1.34. When set, pod-level resources take precedence over container-level ones; the difference is reflected as an additional data point —aggregating at the pod scope shows the true effective resource reservation. For limits, this difference can be negative if the sum of container-level limits exceeds the pod-level limit.

Infrastructure Observability | Kubernetes

Add container runtime name field

Kubernetes platform monitoring now also writes the container.runtime.name field on the Smartscape CONTAINER node.

Platform | Dashboards

ActiveGate Diagnostic dashboard moves to Fleet Management

The ActiveGate Diagnostic Overview dashboard has moved from Dashboards to Fleet Management. The existing dashboard shows a deprecation notice with a link to the new location. It now uses Smartscape Node ID instead of ActiveGate ID for filtering and supports deep-linking from Fleet Management ActiveGate details view; the dashboard automatically pre-filters to the selected ActiveGate.

Software Delivery

ActiveGate container image updated to Red Hat UBI 10 Micro

The containerized ActiveGate base image has been updated from Red Hat UBI 9 Micro to Red Hat UBI 10 Micro.

Software Delivery

Add host entity dimension when monitored by OneAgent

ActiveGate self-monitoring (SFM) metrics now include a host entity dimension when the ActiveGate is monitored by a OneAgent.

Operating system support

Fixes and maintenance

Resolved issues in this release