This page showcases new features, changes, and bug fixes in Dynatrace ActiveGate version 1.343. It contains:
Infrastructure Observability | Kubernetes
CPU and memory request/limit metrics now account for init containers. When init containers require more resources than the running containers, the difference is reflected as an additional data point, so aggregating at pod scope shows the true effective resource reservation.
With this release, the following are the oldest supported ActiveGate versions.
| Support level | Oldest supported version |
|---|---|
1.325 | |
1.319 |
For details, see How long are versions supported following rollout?.
Digital Experience | Synthetic
Chromium 150 is now supported by Synthetic-enabled ActiveGate installed on:
Chrome for Testing 150 is now supported by Synthetic-enabled ActiveGate installed on:
Chrome for Testing 150 is bundled with the Windows ActiveGates installer.
Infrastructure Observability | Kubernetes
ActiveGate now calls the Kubernetes API endpoint only once per minute, down from multiple times per cycle. This reduces API pressure in large clusters and environments with strict rate limits.
Infrastructure Observability | Kubernetes
ActiveGate now supports the new tagging strategy on SaaS.
Known limitations:
Platform
If you're planning or scaling log collection infrastructure, we've updated the sizing guides for the Environment ActiveGate Log ingestion API (JSON and OTLP). These now cover containerized (operator-provisioned) and host-based deployments. The guides provide capacity recommendations to reduce the risk of latency and data loss in production.
Sizing guides for containerized environment ActiveGate: OTLP endpoint, combined scenario (Kubernetes log modules + OTLP API traffic), and routing mode with log module traffic only.
Sizing guides for Host-based Environment ActiveGate on Linux and Windows: JSON and OTLP endpoints, and combined scenario (JSON API + OneAgent log modules).
Documented testing profiles so you can compare their workload against the baselines used for each sizing recommendation.
For details, see Linux ActiveGate sizing guide, Windows ActiveGate sizing guide, and Kubernetes ActiveGate sizing guide.
Platform | API Gateway
The following endpoints are now deprecated on SaaS:
GET /api/v2/activeGates—lists all available ActiveGatesGET /api/v2/activeGates/{agId}—gets details of a specific ActiveGateGET /api/v2/activeGates/groups—lists ActiveGate groupsThese are replaced by the ACTIVEGATE Smartscape node.
For details, see Smartscape.
vsphere.strict.tls.validation is available in the [vmware_monitoring] section in custom.properties. When set to false, which is the default, it accepts any certificate and skips hostname verification, remaining backwards-compatible with self-signed vCenter deployments. When set to true, it validates the vCenter certificate chain and enforces standard hostname verification. Before enabling strict mode, import the vCenter CA certificate into the ActiveGate truststore, since enabling strict mode without importing the certificate will cause vSphere connections to fail. No action is required for existing deployments, as the default behavior is preserved for backwards compatibility. Enabling strict TLS validation is recommended for all deployments where the vCenter certificate can be imported into the truststore. (DAQ-21791)