This page showcases new features, changes, and bug fixes in Dynatrace ActiveGate version 1.331. It contains:
With this release, the following are the oldest supported ActiveGate versions.
| Support level | Oldest supported version |
|---|---|
| Standard Support | 1.313 |
| Enterprise Success and Support | 1.307 |
For details, see How long are versions supported following rollout?.
All | Metrics Ingestion Protocol
All attributes present on the OTLP resource are now ingested as dimensions in Metrics powered by Grail.
The following settings for OTLP metrics ingest are available to tailor the behavior to your needs:
These changes continue to strengthen security and cost tracking with fine-grained access control and cost breakdowns (for example, using dt.cost.costcenter) and prepare your metrics for chargebacks and security monitoring while keeping data management efficient.
To enable this new version of the OTLP metrics ingest, in Dynatrace Classic, go to Settings > Metrics > OpenTelemetry metrics, and turn on Advanced OTLP metric dimensions.
For further details about these changes and their effect on enrichment with the dt.entity.service dimension, see OTLP Metric Dimensions Changes in the Dynatrace Community.
Digital Experience | Synthetic
Chromium 143 is the latest supported version for Synthetic-enabled ActiveGate installed on:
Chrome for Testing 143 is the latest supported version for Synthetic-enabled ActiveGate installed on:
Chromium 143 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.
Digital Experience | Synthetic
To take advantage of performance improvements, latest security vulnerability enhancements, and bug fixes, we've upgraded JRE to version 17.0.17+10.
Infrastructure Observability
ActiveGate Kubernetes monitoring now writes additional fields for the CONTAINER Smartscape node (if available via Kubernetes API):
container.idcontainer.image.namecontainer.image.versionInfrastructure Observability
We improved the outbound performance of ActiveGate by better managing the HTTP connections—we reduced the number of SSL handshakes by re-using HTTP connections more frequently.
Infrastructure Observability | AWS
This ActiveGate release includes an 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 the 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.331.
Software Delivery
ActiveGate on Linux now automatically retries failed updates. If the installation of a newer version of ActiveGate or a module fails, the autoupdater tries again without re‑downloading the installer after 12 hours (initial try and 3 retries).
Software Delivery
We introduced File Access Policy (fapolicyd) management for the ActiveGate installation process. The installer automatically manages ActiveGate rules in the correct order to grant the necessary permissions for the Dynatrace user and group. For more details on File Access Policy management, see Chapter 12. Blocking and allowing applications by using fapolicyd in the Red Hat documentation.
dsfm:active_gate.communication.messages.rejected) was missing part of the rejections related to an unavailable environment when OneAgent was using legacy basic authorization. (DAQ-17842)