03/24/2026 | Press release | Distributed by Public on 03/25/2026 05:19
This page showcases new features, changes, and bug fixes in Dynatrace SaaS version 1.335. It contains:
Platform | Notebooks
Explore records in detail with the new record details panel for Notebooks and Dashboards
In a Dashboards or Notebooks table visualization, you can now right-click any row to select View record details. This displays the selected record, rotated 90 degrees, in a side panel, for a much better overview of records with many fields.
Feature updates
Application Observability | Log Analytics
Log Monitoring Classic end-of-life
With this release, Log Monitoring Classic is automatically upgraded to Log Management and Analytics in SaaS environments that have not ingested logs in the past 90 days. Environments actively ingesting data to Log Monitoring Classic are currently not impacted. This change is the second milestone in the end-of-life for Log Monitoring Classic SaaS.
The next and last milestone will arrive in January 2027, when all remaining Dynatrace SaaS environments with Log Monitoring Classic will be automatically upgraded to Log Management and Analytics.
We recommend upgrading Log Monitoring Classic to Log Management and Analytics ahead of end-of-life, following this guide. See also the first announcement of the end-of-life for Log Monitoring Classic SaaS.
This announcement does not impact Log Monitoring Classic on Dynatrace Managed or Log Monitoring APIs on Dynatrace Managed.
Application Observability | Log Analytics
Understand and optimize Logs usage with the new Usage - Logs ready-made dashboard
Visualize your Logs usage across the platform with the new Usage - Logs ready-made dashboard. With this dashboard, you can now:
Find the new dashboard at Dashboards > Ready-made dashboards > Usage - Logs.
The ready-made dashboard Log query usage and costs is now deprecated and will be removed by the end of June 2026. You can create a local copy to keep using it. Use Usage - Logs going forward.
Application Observability | Services
Service request metrics () are now automatically enriched with primary Grail fields and primary Grail tags whenever these exist on the source span. This includes AWS fields (, ), Azure fields (, , ), GCP fields (, ), and primary tags (). These modifications allow you to set up Segments and permissions in Grail, or use ready-made Segments (for example, for Kubernetes Namespace). They also streamline filtering in all Dynatrace apps, including Notebooks and Dashboards.
Application Security
Updated library to version 1.25.7 in Kubernetes Node Configuration Collector (NCC)
We have updated the library to in Kubernetes Node Configuration Collector (NCC) to address known vulnerabilities. The NCC image was released as version 1.5.4.
Infrastructure Observability | Hosts
Combined process grouping rules
This update combines the Simple detection rules, Advanced detection rules, and Declarative process grouping rules into integrated process grouping rules. You can now overwrite built-in detection rules and redefine process grouping and detection to activate split, merge, or no-monitoring. This combination now allows grouping based on environment variables, processes, properties, and user-defined strings. The same rules now apply across all agents and modes, reducing uncertainty about the right settings to change the default grouping. See more in Declarative process grouping.
Platform | CoPilot
New tenants: Generative AI enabled by default
Generative AI is now enabled by default for all new tenants. This change allows admins to opt out rather than requiring them to opt in to use features like DQL generation in Notebooks or Dashboards, and Dynatrace Assist in non-agentic mode.
To use agentic mode in Dynatrace Assist, admins still need to enable it explicitly in Settings.
This change only affects tenants created after Dynatrace SaaS version 1.335is rolled out. For older tenants, both agentic and generative AI will remain disabled unless they were explicitly enabled before.
Platform | DQL
New aggregation for histogram metrics
You can now use the aggregation with the and commands to calculate the fraction of observations below a specified threshold. This aggregation performs the inverse of the aggregation. For example, if your p99 response time is 1.5 seconds, then the fraction of response times below 1.5 seconds is 0.99 (or 99%). is particularly useful if you have response time SLOs.
For details, see the DQL commands timeseries and maketimeseries.
Platform | Dynatrace Intelligence
Problems app: New Affected entities column
Problems now includes an Affected entities column in the problem table, visible by default. Entity names are displayed with direct links, so you can identify impacted services, apps, or synthetic tests and navigate to them. Selecting an entity opens contextual actions such as View service and Open with.
Platform | Dynatrace Intelligence
You can now add comments directly to problems to better support coordination during incident remediation.
With this update, you can:
Platform | Notebooks
Keep important columns in view with pinned columns in tables
In Dashboards and Notebooks table visualizations, you can now pin columns to keep them visible while scrolling horizontally.
This can be especially useful when working with larger result sets containing many fields.
As part of this change, drag-and-drop column reordering has been removed, but you can still reorder columns using the Visibility and order options.
Platform | Settings
Metrics catalog in Settings
Settings now includes a metrics catalog, giving administrators a central place to browse and manage all metrics in their environment - both built-in and custom. Use the catalog to search and sort across your full metrics inventory, and inspect key metadata including metric key, kind, display name, description, and unit. Where needed, you can edit display name, description, and unit directly to keep your metrics organized and meaningful across teams.
Breaking changes
Application Observability
SemDict-compliant attributes now replace undocumented ones in the service_mesh namespace
Service mesh spans were previously marked with undocumented attributes in the namespace. We updated them to use the new documented semantics. This could affect custom DQL queries and pipeline configurations.
Platform | DQL
Smartscape IDs are no longer directly comparable with strings in DQL
To compare a Smartscape ID with a string, especially a string literal, convert the string to a proper Smartscape ID, for example:
fetch logs
| filter dt.smartscape.host == toSmartscapeId("HOST-0000000000000001")
This change affects the DQL comparison operators (, , , , , ), the operator, and the function, as well as join conditions (, , ).
Platform | OpenPipeline
OpenPipeline legacy config API sunsets on June 29, 2026
The legacy configuration API for OpenPipeline (see GET a configuration) was deprecated in November 2025 (with ) and replaced with a configuration based on the Settings API. This immediately delivered fine-grained permissions, and since then, we have added new features to OpenPipeline that can only be configured via the new Settings API.
On June 29, 2026, we will deactivate the legacy API and migrate all tenants that were not previously migrated to the new Settings-based configuration API.
Fixes and maintenance
Resolved issues in this release (SaaS)