What's new in Dynatrace Managed 1.346

• Release notes
• 5-min read
• Published Aug 25, 2026
• Rollout start on Aug 31, 2026

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

Feature updates

Digital Experience | Synthetic

Screenshots now sent directly from your cluster to Amazon S3

Screenshots captured in your Dynatrace environments are now uploaded to Amazon S3 directly from the cluster, replacing the previous flow where the upload was handled by VUC. This change eliminates the need to pass AWS credentials to VUC, reducing the credential exposure surface and improving overall security.

Infrastructure Observability

Redesigned Azure page for quicker insights

We’re excited to announce a redesigned Azure page, bringing broader visibility, smoother navigation, and a more intuitive monitoring experience to your infrastructure performance workflows.

Platform

Cassandra nodes upgrade to version 4.1.12

The Cassandra nodes are upgraded to version 4.1.12, delivering critical bug and security fixes. No manual user intervention or downtime is required—the upgrade happens via rolling updates as a part of normal version updates.

Platform

Track tenant token rotation status and receive daily alerts

You can now query the current status of a tenant token rotation in your Dynatrace Managed environment using the new api/v2/tenantTokenRotation/status endpoint. While a rotation is in progress, a severe Cluster event is raised daily for the duration of the rotation, so cluster administrators stay informed until the rotation completes.

Previously, there was no way to check whether a rotation was in progress. An incomplete rotation persisted undetected and directly affected monitoring continuity.

Platform

Redesigned user authentication pages in the Cluster Management Console

You can now manage user authentication in the Cluster Management Console through a redesigned experience. Across the User authentication pages, the filters, data tables, and actions look and behave consistently, and when you save or discard a change, it takes effect immediately, just like your environment settings.

Platform

Simplified local self-monitoring environment

Local self-monitoring environments now show only the relevant capabilities that are available in the environment. This affects the environment’s Settings, main menu, and preset dashboards.

Platform

Stay informed about unsupported Dynatrace Managed product versions

When you're using an unsupported version of Dynatrace Managed, you will be informed with a notification and a special tag on the Licensing page.

Platform | Dashboards

Keep your management zone filter when you drill into remote dashboards

You can now drill down from an aggregated dashboard to a dashboard in a remote environment and keep your management-zone filter in place. The filter is applied automatically when you open the remote dashboard, so your monitoring context stays consistent as you navigate across environments. You can keep filters for multiple management zones simultaneously.

Previously, the filter was lost in the remote environment, and you had to select the same management zone again in each remote environment. The filter now carries over only when a management-zone name matches exactly between the source and remote environments.

Platform | Problems

Send problem notifications to IPv6 webhook endpoints

You can now target IPv6 endpoints with problem notification webhooks, so your notification pipeline works in environments that run IPv6-only networks. The webhook URL field in Settings > Integrations > Problem notifications accepts IPv6 bracket notation alongside standard IPv4 addresses. Existing IPv4 webhook configurations continue to work without changes. Dynatrace itself continues to operate in an IPv4 setup. To enable IPv6 webhook support, run the installer with --enable-ipv6-webhooks on. For existing installations, use --enable-ipv6-webhooks off to revert to IPv4-only webhooks.

Breaking changes

Application Observability

Connections from OneAgent version 1.215 and earlier are rejected

Dynatrace now rejects connections from OneAgent version 1.215 and earlier. Action plan: If you're running OneAgent version 1.215 and earlier, upgrade to a supported OneAgent version to avoid data loss and connectivity issues, and to benefit from enhanced security and features unavailable in earlier OneAgent versions.

For details, see End-of-life announcements.

Application Observability | Distributed Tracing

HTTP failure detection extended to FaaS services

HTTP failure detection now applies to FaaS services (AWS Lambda, Azure Functions, and GCP Cloud Functions) with HTTP data. After this update, you may see a higher failure rate in your environment. This is expected—issues with these services are now detected and reported for the first time.

Software Delivery

Select a container registry in the Kubernetes deployment form

When configuring Kubernetes or OpenShift monitoring in the Managed deployment form, you can now select the container registry from a dropdown.

Based on your selection, Dynatrace generates a Helm install command with the appropriate image locations.

The built-in cluster container registry will be shut down on January 1, 2028, and will no longer function because it doesn't support ARM architectures. Action plan: Migrate to Amazon ECR or Docker Hub.

Fixes and maintenance

Resolved issues in this release

Operating systems support

Dynatrace API

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