Dynatrace Managed release notes version 1.322

  • Release notes
  • 10-min read
  • Rollout start on Sep 1, 2025

Rollout start: Sep 1, 2025

This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.322.

Announcements

Platform | Metrics

Upcoming native support for OpenTelemetry and Prometheus histograms

Starting with Cluster version 1.324, Dynatrace introduces native support for OpenTelemetry and Prometheus histograms, including automatic percentile calculation. This enhancement enables faster detection of performance outliers and simplifies observability workflows.

Breaking change for existing histogram metrics:

  • Existing histogram metrics will no longer be updated, but they will remain available for historical visualization on dashboards, ensuring continuity and data retention. The new native histogram metrics will be exposed under distinct metric keys, each suffixed with .histogram.

  • If an existing metric already ends with .histogram or _histogram, it will no longer receive new data points. To use the new histogram functionality under the same metric key, you must delete the existing metric using the Metrics API - DELETE a custom metric. After deletion, a new histogram metric will be automatically created under the same key.

In Dynatrace, in your Local-Self-Monitoring environment, you can use the following query in Data Explorer to see which histogram metrics have been ingested:

isfm:active_gate.metrics.ingest.explicit_bucket_histogram.layout.series
:splitBy(metric_key,"dt.tenant.uuid",data_source)
:sort(value(auto,descending))
:limit(100)

This query requires Cluster version 1.314+ to be installed for the metric to be available.

New features and enhancements

Application Observability | Services

Define custom services for short-lived Go processes via web UI

You can now define a custom service for short-lived Go processes through the web UI. Similarly to Java, the Define entry point manually function is now available for Go.

Previously, defining a custom service for short-lived Go processes was only possible via the Configuration API.

For details, see Service detection rules.

Digital Experience | Session Replay

Session Replay: mobile browser UI improvement and iframe handling

A session recorded from a mobile browser shows the unrecorded gaps on the screen instead of fake UI elements (keyboard, navbar).

Sessions recorded on a desktop from a non-top iframe with a long resolution are zoomed to the interacted part.

Digital Experience | Session Replay

Added new placeholders for frameset and canvas elements

Session Replay now has placeholders to replace the unsupported frameset and canvas elements.

We have also added legends for both placeholders on the image placeholders legends box.

Infrastructure Observability | Hosts

Python module and script fields added to a process group

Python module and script fields are now available for Python process groups and processes.

Infrastructure Observability | Extensions

Extension Execution Controller enabled by default

The Extension Execution Controller (EEC) is now enabled by default in new environments. There are no changes for existing environments.

Platform | Dashboards

Share dashboards with IAM policy–based users and groups

In addition to sharing dashboards with role-based users and groups, you can now share dashboards with IAM policy–based users and groups through the dashboard-specific share setting.

Platform | Metrics

Increased default metric dimensions limit for anomaly detection static threshold model

The default metric dimensions limit for static threshold configurations has been increased from 1,000 to 2,000.

Breaking changes

Application Observability | Services

Service detection v2: Endpoint detection rules have been updated

With this release, only service entry points (server/consumer spans) become endpoints, excluding outbound calls to other services. Endpoint names also change to include the HTTP method.

Results:

  • Focuses metrics on actual service health rather than total system activity.
  • Reduces endpoint counts and improves service performance representation.

Availability:

  • New environments get these new rules automatically.
  • Existing environments must opt in via Settings.

To preview changes before opting in, use the dashboard attached to our Dynatrace Community post.

For details, see Service Detection v2.

Digital Experience | RUM Web

AMP application monitoring no longer supported

Support for monitoring AMP (Accelerated Mobile Pages) applications has been discontinued. As a result, AMP applications are no longer available within your environments.

Dynatrace API

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

Operating systems support

    Future Dynatrace Managed operating systems support changes

    The following operating systems will no longer be supported starting 01 January 2026
    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

    Resolved issues

    General Availability (Build 1.322.58)

    The 1.322 GA release contains 14 resolved issues.

    ComponentResolved issues
    Cluster12
    Synthetic Monitoring1
    core1

    Cluster

    • Monitors with the `certificateExpiryDate` condition were wrongly allowed by the REST API with `"passIfFound": true`, which is not allowed and caused unexpected events. The issue is now fixed and API validation matches the web UI to block this setting. (DEM-13306)
    • We fixed the issue where the generic entity `last seen timestamp` can be different in caching, compared to Cassandra. (MGD-5724)
    • Improved tag parsing in alerting profiles and metric key-based metric events. (DI-21359)
    • Users without IAM read permissions for log agent feature flags can now access the "Log ingest rules" page. (OA-52119)
    • Standalone/application-only OneAgents under some circumstances were deactivated when, according to the configuration, they should have been active. This has been corrected; the affected OneAgents should become active automatically again. (MGD-6536)
    • Resolved an issue where an IllegalArgumentException ("key is not a column in this row") could be thrown by the Settings framework when attempting to read from a Cassandra instance in an inconsistent state. (PS-35837)
    • Resolved an issue with upgrading Dynatrace Managed from version 1.318 to version 1.320, which in some cases was stuck on the firewall process starting. (MGD-6570)
    • Fixed an issue where Distributed Traces Classic was not applying the proper problem timeframe. (APPOBS-9148)
    • Ensured scrolling by fragment when any event is selected from the timeline. (DEM-12569)
    • Restored correct UI flow for OneAgent bulk action settings for environments where new OneAgent communication settings flow is enabled. (MGD-6299)
    • Resolved an issue that caused slow loading of distributed traces in the web UI for on-demand analysis. (MGD-6243)
    • Fixed an issue in Session Replay where some pages in the recording would appear completely blank. (DEM-13641)

    Synthetic Monitoring

    • Updated `event.description` field in Grail for Synthetic HTTP monitor outage events to include the `api.fail` message when present, ensuring consistency with problem representation in classic Dynatrace Synthetic monitoring. (DEM-12107)

    core

    • Updated container group ID calculation for Azure Container Apps. In addition to using `CONTAINER_APP_NAME`, which is only unique within a single resource group, the `CONTAINER_APP_ENV_DNS_SUFFIX` is now also incorporated into the container group ID calculation. For the container group name, the `CONTAINER_APP_NAME` is used. (OA-49967)