What's new in Dynatrace Managed version 1.330

  • Release notes
  • Published Jan 09, 2026
  • Rollout start on Jan 19, 2026

New versions are rolled out within configurable maintenance windows.

Rollout startCurrently supported
Version 1.330Jan 19, 2026Yes
Version 1.328Dec 2, 2025Yes
Version 1.326Oct 27, 2025Yes
Version 1.324Sep 29, 2025Only with Enterprise Success and Support

This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.330. It contains:

Feature updates

Account Management

Monitor your cluster license usage

We have added a dashboard to your cluster's local self-monitoring environment, which allows you to track the license usage of your host units, Davis data units (DD), and Digital Experience Monitoring (DEM) units under classic licensing.

We have also added specific billing metrics for each license unit, so you can alert on license events (for example, when units are about to run out) using metric events. For details on billing metrics and how to define license events, see Dynatrace classic licensing.

Cluster license usage dashboard

Application Observability | Distributed Tracing

Set and override OneAgent masking at the host group level

OneAgent masking can mask data at first contact before it leaves a monitored process. To allow you to configure it in multiteam and multidepartment environments, we made it possible to set and override it at the host group level in addition to the already existing environment, Kubernetes cluster/namespace, and process group levels. This is especially convenient when managing hundreds of applications.

Platform

Intuitive zoom functionality for Data Explorer charts

We have added the ability to zoom in or out directly on charts in the Data Explorer. To zoom in on a chart, select the desired start point, hold down the mouse button, and drag to the desired endpoint. Release the mouse button; a confirmation dialog for the zoom interval should appear.

Once you have zoomed in, you can use the revert button to return to the previous timeframe.

Zoom functionality on Data Explorer charts

Platform

Improved accuracy in dimension limit monitoring for metrics

Usage of custom metrics with a steady flow of new dimension values (such as Kubernetes pod UIDs) could display incorrect patterns in self-monitoring, including sudden increases followed by drops.

With this update, dimension limits are now calculated accurately, providing clearer and more reliable insights into your metric usage.

Platform

Suggestions for entity selectors in Settings

Automatically applied tags, management zones, and SLO definitions now support entity selector suggestions. Instead of manually typing out entity selectors, you can use this auto-complete feature, which suggests available filters, operators, and values.

entity selector suggestions

Platform

New Metrics API v2 endpoint for deleting outdated metrics

The Metrics API v2 now includes a new endpoint that allows you to delete metrics that haven't been written in a given number of days. Here’s what you can do:

  • Use DELETE /api/v2/metrics to delete ingested metrics.
  • Use the metricSelector parameter to choose specific metrics.
  • Use wildcards to delete metrics with a prefix or all metrics by specifying *.
  • Use the minUnusedDays parameter to define how many days a metric must go unused before it’s deleted.

Example: To delete all metrics not written in the last 60 days:

DELETE /api/v2/metrics?metricSelector=<your-selector>&minUnusedDays=60

Platform | OneAgent

OneAgent version compatibility check

OneAgent Health now displays the lowest and highest compatible OneAgent versions with this Managed cluster. Additionally, a warning message is issued if a OneAgent version is too low or too high, allowing you to react and quickly connect a OneAgent with a compatible version.

Breaking changes

Infrastructure Observability | Extensions

The following deprecated endpoints have been removed from the Environment API v2:

  • /extensions/{extensionName}/environmentConfiguration/events
  • /extensions/{extensionName}/monitoringConfigurations/{configurationId}/events.

Platform

The in-product live chat has been replaced by an external link to the Dynatrace Support Center. In the Dynatrace Support Center, you can contact our product specialists at any time with questions about Dynatrace.

Platform

Metric fileDescriptorsPercentUsed is no longer split by PID

For performance reasons, the PID dimension was removed from the fileDescriptorsPercentUsed metric. This means the metric can't be split by PID anymore.

Metric key: builtin:tech.generic.handles.fileDescriptorsPercentUsed

Fixes and maintenance

Resolved issues in this release

  • In the case of classic K8s log monitoring, the log monitoring modules are not included in the host Units license and are also not billed. However, they were incorrectly included in the host unit quota check, potentially leading to misleading information about quota usage. Therefore, we excluded the log monitoring modules from the host unit quota check (MGD-8983)
  • Fixed installer packages that weren't synchronized correctly between nodes if a script file without a semantic version in the filename was present in the Dynatrace Managed server installer folder. (MGD-8354)
  • Resolved an issue with application-only deployments when multiple code modules could overwrite each other's OneAgent version on the same host. (MGD-6868)
  • Reliable browser monitor auto-login: Fixed a bug in the JavaScript step of the auto-login browser monitor, preventing crashes when the monitor fails, for a smoother monitoring experience. (DEM-18430)
  • Consistent handling of whitespace endpoints: Service detection v2 spans now treat endpoints consisting of all whitespace characters the same as empty endpoints, resulting in no endpoint.name being assigned. This update ensures consistent span behavior, with no impact on metric generation. (APPOBS-30130)

Operating systems support

Future Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 June 2026
The following operating systems will no longer be supported starting 01 July 2026

Past Dynatrace Managed operating systems support changes

The following operating systems are no longer supported since 01 July 2025
The following operating systems are no longer supported since 01 December 2025
The following operating systems are no longer supported since 01 January 2026

Dynatrace API

To learn about changes to the Dynatrace API in this release, see: