With this release, the following are the oldest supported ActiveGate versions.
| Support level | Oldest supported version |
|---|---|
| Standard Support | 1.311 |
| Enterprise Success and Support | 1.305 |
For details, see How long are versions supported following rollout?.
This page showcases new features, changes, and bug fixes in Dynatrace ActiveGate version 1.329. It contains:
Digital Experience | Synthetic
Chromium 142 is the latest supported version for Synthetic-enabled ActiveGate installed on:
Chrome for Testing 142 is the latest supported version for Synthetic-enabled ActiveGate installed on:
Chromium 142 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.
Infrastructure Observability | Kubernetes
We’ve added back-off logic for Kubernetes API calls to improve performance and reduce load. If the API returns a 404 (Not Found) or 403 (Forbidden) error, the system delays retries for up to a maximum of 60 minutes. Currently, this applies only to the Kubernetes enhanced object visibility preview release.
Software Delivery
This ActiveGate release includes an update to JRE Adoptium Temurin 17.0.18, providing the latest security updates and improvements.
Infrastructure Observability | AWS
This ActiveGate release includes a partial update to the AWS monitoring module, which now utilizes the AWS SDK for Java v2.33.5. To ensure continued security, performance, and access to critical updates, we recommend updating all environments running the AWS monitoring module. As SDK V2 only supports STS regional endpoints in order for AWS monitoring to work, make sure you have enabled STS endpoints for regions you want to monitor.
If your Dynatrace environment has automatic updates enabled, no manual action is required—the update will occur via rolling updates.
If updates are managed manually, follow the instructions in Update ActiveGate to update to ActiveGate version 1.329.
Application Observability | Log Analytics
The JSON Log Ingestion API (/logs/ingest endpoint) will be updated with ActiveGate version 1.332.
Currently, the list of fields treated as a timestamp contains the following keys: timestamp, @timestamp, _timestamp, eventtime, date, published_date, and syslog.timestamp. This list will be extended to include the following keys: time, epochSecond, startTime, datetime, ts, @t, and timeMillis.
The OTLP Log Ingestion API (/otlp/v1/logs Endpoint) will be updated with ActiveGate version 1.332.
Currently, log severity is determined based on the OTLP message severity or severityText fields, or on one of the following Body attributes (if the Body is a map): log.level, status, severity, level, or syslog.severity. With the upcoming change (in ActiveGate version 1.332), Dynatrace will additionally attempt to extract severity from the OTLP Log Record attributes using the mentioned keys.
Currently, the log time is determined based on the OTLP message timestamp field or on one of the following Body attributes (if the Body is a map): timestamp, @timestamp, _timestamp, eventtime, date, published_date, or syslog.timestamp. With the upcoming change (in ActiveGate version 1.332), this list of attributes will be extended to include: time, epochSecond, startTime, datetime, ts, @t, and timeMillis. Additionally, Dynatrace will attempt to extract the time from the OTLP Log Record attributes in the same way as from the Body.
Infrastructure Observability | Kubernetes
The following deprecated attributes were removed from ActiveGate Kubernetes API Monitoring. Use the equivalent attributes as defined in the Semantic Dictionary:
dt.kubernetes.workload.nameis replaced by k8s.workload.name.dt.kubernetes.workload.kindis replaced by k8s.workload.kind.dt.kubernetes.node.nameis replaced by k8s.node.name.dt.kubernetes.cluster.nameis replaced by k8s.cluster.name.