This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.338. It contains:
Platform | Dashboards
Dynatrace Managed now supports a dedicated histogram chart in Data Explorer and Dashboards for visualizing histogram metrics.
With this new chart type, you can:
This enhancement improves observability into the shape and spread of your data, complementing existing chart types such as line and bar charts.


Platform
As part of this release, the Cassandra nodes are upgraded to version 4.1.11 to provide critical bug and security fixes.
No manual user intervention or downtime is required; the upgrade occurs via rolling updates as part of normal version updates.
Platform
You can now convert an existing offline Dynatrace Managed cluster to an online cluster without redeployment. Previously, you had to choose the connectivity mode during deployment and could not change it afterward. A conversion script is now shipped with Dynatrace Managed that allows administrators to change this connectivity mode.
For more details, see Convert Dynatrace Managed cluster from offline to online.
Platform
In the Dynatrace web UI (for example, on the host, container, or service details page), select Properties and tags to find the monitored entity ID as the first property. This monitored entity ID is helpful when querying a specific monitored entity using the entity selector.

Platform | Settings
Many Configuration API endpoints are now covered by the Settings endpoints in the Environment API v2. Affected Configuration API endpoints now have deprecation notices.
We recommend migrating to the Environment API v2 endpoints for a more robust integration. Review the Configuration API reference to identify affected endpoints and plan your migration to Environment API v2.
Digital Experience | Synthetic
We removed the performanceMetric parameter from the builtin:synthetic.browser.enablement schema and from EnablementDto on the Synthetic Monitors Environment API v2. This parameter defined which metric was used to display performance charts in the Dynatrace web UI and check performance threshold violations.
Performance alerts continue to use the dt.synthetic.browser(.step).duration metric with no changes in functionality.
500 error instead of a 504 error in case of a timeout. (LIMA-43865)429 Too Many Requests HTTP error code are now retried up to two times in 15-minute intervals. This reduces the likelihood of problems remaining open in ServiceNow when ServiceNow can't initially process notifications. (DI-27261)synthetic.yaml template for OpenShift, which was pointing to a nonexistent image (dynatrace/activegate:<version>) instead of the correct one (dynatrace/dynatrace-activegate:<version>). (DEM-24277)appVersion would return HTTP 400 errors. (DEM-23630)To learn about changes to the Dynatrace API in this release, see: