Rollout start: May 12, 2025
This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.314.
Dynatrace Cluster
You can ensure compliance with your regulations by scanning the Dynatrace Managed SBOM for vulnerabilities.
The SBOM contains all third-party libraries used by Dynatrace Managed and their versions.
A new SBOM is provided with each version. It is part of the Managed installer and conforms to the CycloneDX standard.
The SBOM filename is:
/opt/dynatrace-managed/installer/dynatrace-managed-<version>/dynatrace-managed-sbom.cdx.json
Dynatrace Cluster
As part of this release, the used compression format of timeseries data in Cassandra will be switched from LZ4 to ZSTD. According to load-testing, this can reduce required disk space considerably.
Note: reduction in disk usage will not be instant, but rather will happen gradually over the course of one month, as only new data will be written with the new compression algorithm.
No manual user invention or downtime is necessary. The switch happens automatically as part of normal version updates.
Dynatrace Cluster
A new periodic worker applies tags, management zones, and naming rules to recently created monitored entities faster. This worker runs continuously and considers all monitored entities created in the last 30 minutes and seen in the last 2 hours.
It is automatically enabled by default for all Dynatrace Managed environments. No additional configuration is required.
Dynatrace Cluster
As part of this release, Dynatrace Cluster Server nodes will be upgraded to run with JDK 21 instead of JDK 17.
No manual user-invention or downtime is necessary. The upgrade should happen via rolling updates as part of normal version updates.
Internal testing showed a considerable reduction of time spent for Java garbage collection, so the update can lead to improved performance of the Dynatrace Cluster Server process.
Digital Experience | Synthetic
The default value for the Accept any SSL certificate property of the HTTP monitor request was changed to false, so the SSL certificate will be validated for newly created monitors.
Application Observability
Managing and browsing your calculated service metrics is now easier and more efficient—especially for environments with many metrics. Here’s what’s new in the Calculated service metrics settings:
These improvements save you time, provide better visibility into your calculated service metrics, and make managing them a streamlined experience.
Platform | Davis
Events that don't trigger a full root cause analysis will no longer wait 3 minutes before notifying. The main cases for this are custom triggered events, such as an AVAILABILITY_EVENT via the REST API.
In addition, the dt.davis.analysis_trigger_delay is now preferred over the internally defined three-minute default for some availability-type events. If dt.davis.analysis_trigger_delay is set, it is the only delay considered for root cause analysis.
Digital Experience
In general, we recommend the deployment of complete synthetic private locations to support the execution of all types synthetic monitors (HTTP, browser, NAM).
If you don't need to run browser monitors, consider deploying your location in browserless mode. This mode deploys the location (or ActiveGate belonging to it) without a browser, reducing hardware requirements. However, browser monitors can't run on a browserless location.
Consider browserless locations as an alternative to standard synthetic private locations when you’re focused purely on:
To learn about changes to the Dynatrace API in this release, see: