Try it free

What's new in Dynatrace SaaS 1.341

  • Release notes
  • 15-min read
  • Published Jun 09, 2026
  • Rollout start on Jun 16, 2026 (planned)
Pre-release information

This is an ongoing summary of changes in this planned release. Check back here at GA for the final version.

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

  • Feature updates: 31
  • Breaking changes: 7
  • Fixes and maintenance: 8 (1 vulnerability)

Feature updates

Application Observability

Log pattern analysis (Preview)

In Logs Logs, you can now aggregate your query results into patterns of data that show similar logs clustered together. This allows you to:

  • Quickly focus on similar or recurring errors to troubleshoot faster
  • Reduce thousands of similar logs to a handful of patterns to cut through the noise
  • Recognize changing parts of the log pattern (token), including its datatype, to focus your next steps of analysis
  • Reuse the generated DPL for the log pattern for other queries or in OpenPipeline

This is available as a preview.

Application Observability | Distributed Tracing

Distributed Tracing app: Improved visualization of errors and failures within Single Trace View

In Distributed Tracing Distributed Tracing, we have improved the visualization of errors and failures within Single Trace View.

Application Observability | Log Analytics

View trace details in context while investigating logs

When investigating a log entry with trace context in Logs Logs, you can now open the associated trace details directly within Logs Logs. A button with a waterfall icon—rather than the Distributed Tracing Distributed Tracing icon—signals that you stay in context rather than navigate away.

Application Observability | Open Telemetry

OpenTelemetry version update

We have updated opentelemetry-proto to version 1.10.0.

Digital Experience

New ready-made user action alert to monitor performance degradation

You can use a new, ready-made alert type to monitor user action performance degradation at the frontend level.

Digital Experience

New frontend.name and dt.smartscape_id properties

We have added support for the new frontend.name and dt.smartscape_id properties for frontend alert events.

Digital Experience

New traffic and ANR alerts

We have added new traffic and ANR alerts for frontends.

Digital Experience

Select static, seasonal, or auto-adaptive analyzer on all alerts

You can now select between a static, seasonal, or auto-adaptive analyzer based on all alerts, and configure your own static threshold.

Digital Experience | Users & Sessions

New session definition

We have introduced significant improvements in session handling:

  • Sessions with at least one user action or navigation are considered valid sessions and serialized.
  • A session with a single user action or navigation is tagged as a bounce.

Infrastructure Observability | Clouds

Promotion for Databases in Clouds

If Clouds Clouds detects a database in your cloud environment, for example, an AWS RDS instance, that isn't monitored by the Databases Databases, Clouds Clouds now displays a banner recommending that you add database monitoring for that resource. Selecting the banner takes you directly to the setup flow so you can monitor the database with full Smartscape-based visibility and view it in the Databases Databases.

Infrastructure Observability | Databases

Database app uses license wall to get new Smartscape features

The Databases app requires an extension update and acceptance of the DATABASE_MONITORING setting for DPS customers to access the new features offered exclusively in the new Explorer view.

Infrastructure Observability | Extensions

Extensions with Unified Analysis pages for Smartscape

Extensions can now ship the Unified Analysis pages for Smartscape.

Infrastructure Observability | Hosts

New OS Service property keys

We have introduced new os_service.* property names for events and availability metrics in addition to the old dt.osservice.* names, which eventually will be deprecated on Dynatrace SaaS.

Infrastructure Observability | Hosts

Host entity in Smartscape on Grail receives two new fields: sku and logical_cores

The host entities in Smartscape on Grail have two new fields: sku (for example, t3.small) and logical_cores (for example, 4).

For more information, see Smartscape - Core Entities.

Infrastructure Observability | Hosts

Host entities from z/OS receive additional information in Smartscape on Grail

The following fields are added to host entities coming from z/OS:

  • zos.cpu_model_number
  • zos.cpu_serial_number
  • zos.system_name
  • zos.virtualization
  • zos.total_general_purpose_processors
  • zos.total_physical_memory
  • zos.total_ziip_processors

For details, see Global field reference.

Infrastructure Observability | Infrastructure & Operations

Fast Grail-powered inventory Explorer in Infrastructure & Operations

Infrastructure & Operations Infrastructure & Operations has a new Explorer, fully powered by Grail, that provides significant performance improvements. It requires OneAgent version 1.337+ as well as the latest versions of technology extensions (there’s a new major version for each).

The existing Explorer will be retained temporarily in a separate tab for backward compatibility.

Infrastructure Observability | Infrastructure & Operations

New REST API serving public URIs for Dynatrace images

We have added a new REST API to provide URIs for the images used in Dynatrace components.

Infrastructure Observability | Kubernetes

Container entities indicate containerization type used to run them

The container entities in Smartscape on Grail have a new field, container.containerization_type (example value: cri-o), indicating which containerization type is used to run the container.

For more information, see Smartscape - Core Entities.

Infrastructure Observability | Kubernetes

New security tab in the Kubernetes app

Kubernetes (new) Kubernetes version 1.42.0+ has a new security tab that replaces the Vulnerability tab in the Explorer. In Explorer (Classic), the Vulnerability tab remains.

Platform

New self-monitoring metric measuring metric data points ingest

You can now track the number of ingested metric data points, broken down by metric key, metric source, cost allocation, and other dimensions. This is made available via the self-monitoring metric dt.sfm.metrics.ingest.datapoints.

Platform | DQL

Extended meta information on data objects in Grail

We introduced the new field usable_with in the output of

fetch dt.system.data_objects

It contains an array listing the DQL commands the data object can be used with.

Platform | OpenPipeline

OpenPipeline pipeline limited to 1,000 processors

In OpenPipeline, a pipeline is now limited to 1,000 processors.

Platform | OpenPipeline

Enhanced log parsing for Azure SQL Database

We have enhanced log parsing for Azure SQL Database.

Platform | Platform Services

Add up to 100 external requests allowlist entries

You can now add up to 100 entries to your external requests allowlist, double the previous limit of 50. This lets you connect even more integrations and add finer-grained patterns. Existing allowlist entries are preserved, and the new limit applies across all environments.

Platform | Platform Services

Schedule maintenance windows to separate planned changes from real incidents

You can now schedule maintenance windows in Dynatrace to mark planned deployments, upgrades, and load tests. One-time and recurring windows are supported. For recurring windows, you can use AutomationEngine scheduling rules and calendars to model complex patterns, such as business-hour exclusions or rolling release cycles.
During an active window, Dynatrace automatically enriches matching telemetry with maintenance metadata. Use it to filter dashboards, adjust workflow logic, and distinguish planned disruptions from real incidents. Windows are persisted as events in Grail, so you always have a complete maintenance history without needing to keep old configurations around.
Maintenance windows are available in Early Access. Problem suppression, synthetic disabling, and SLO time exclusions are planned for upcoming releases.

Platform | Segments

Improved navigation and sharing in Segments

The Segments app now opens in a new browser tab when accessed from the segment selector (for example, in Dashboards Dashboards or Notebooks Notebooks), replacing the previous modal overlay. This lets you keep your current context while managing segments.

Additionally, segments in the management list are now rendered as standard links, enabling:

  • Right-click > Open in new tab or Copy link address.
  • Cmd/Ctrl+click to open in a new tab.
  • Shareable, stable URLs for individual segments.

These changes align Segments with standard web navigation patterns, making it easier to share segment configurations with teammates and to work with multiple segments in parallel.

Platform | Smartscape

Explore all entity relationships in a single topology view

The new All topology view shows all relationships for a given Smartscape node in a single graph—the infrastructure stack, communication flows, and relationships such as monitoring, load balancing, routing, and API dependencies. Where the existing vertical and horizontal views each focus on a specific subset of relationships, the All topology view gives you the complete picture of what's connected and how. Available from any Smartscape node in any app across the Dynatrace platform.

Platform | Smartscape

Narrow down Smartscape views with ad-hoc filters

Ad-hoc node and edge filters let you focus Smartscape views on what matters. Filter by node type, cloud and infrastructure labels, team ownership, environment, and other node and edge properties so each view reflects how your business is structured. Filters work alongside segments for quick, focused investigations. Filters are saved to the URL, so you can bookmark and share views with colleagues—segment, timeframe, and filters preserved.

Screenshot: it shows how you can adhoc filter Smartscape views.
Screenshot: it shows how you can adhoc filter Smartscape views.

Software Delivery

Metrics enriched with dt.openpipeline.source

Metrics ingested from extensions are now enriched with a new dt.openpipeline.source=extension:<extension_name>.

Threat Observability | Security events

CrowdStrike integration

Dynatrace now integrates with CrowdStrike to ingest detection findings.

Threat Observability | Security events

Checkmarx integration

Dynatrace now integrates with Checkmarx.

Breaking changes

Account Management

Endpoint Deprecation

Following Endpoints will be deprecated on Mon, 15 Jun 2026 00:00:00 GMT and be sunset on Mon, 11 Jan 2027 00:00:00 GMT:

  • For GET /sub/v2/accounts/AccountUuid/subscriptions/SubscriptionUuid/environments/cost, the alternative is: GET /sub/v3/accounts/AccountUuid/subscriptions/SubscriptionUuid/environments/cost.
  • For GET /sub/v2/accounts/AccountUuid/subscriptions/SubscriptionUuid/environments/usage, the alternative is: GET /sub/v3/accounts/AccountUuid/subscriptions/SubscriptionUuid/environments/usage
  • For POST /v1/accounts/AccountUuid/notifications, the alternative is: GET /v2/accounts/{accountUuid}/notifications.
  • The POST /iam/v1/repo/{levelType}/{levelId}/policies/validation endpoint is unavailable within the global level. Validation moved to create/update policy endpoints.
  • The POST /iam/v1/repo/{levelType}/{levelId}/policies/validation/{policyUuid} endpoint is unavailable within the global level. Validation moved to create/update policy endpoints.
  • GET /iam/v1/accounts/{accountUuid}/groupUuid}/permissions. Consider migrating your role-based permissions to IAM policies. For more information, see: Learn how to manage policies.
  • POST /iam/v1/accounts/{accountUuid}/groupUuid}/permissions. Consider migrating your role-based permissions to IAM policies. For more information, see: Learn how to manage policies.
  • PUT /iam/v1/accounts/{accountUuid}/groupUuid}/permissions. Consider migrating your role-based permissions to IAM policies. For more information, see: Learn how to manage policies.
  • DELETE /iam/v1/accounts/{accountUuid}/groupUuid}/permissions. Consider migrating your role-based permissions to IAM policies. For more information, see: Learn how to manage policies.

Application Security

Stricter timestamp validation for security.events

Ingested security.events need to have a timestamp within a range of -1h/+10mins. Security.events with an older timestamp are dropped. Security.events with a new timestamp are set to +10mins. Previously, the accepted timerange was -24h/+10mins. It is still possible to omit the timestamp and let OpenPipeline automatically set it to the current one.

Application Security

AbuseIPDB and VirusTotal apps are deprecated — migrate to Security Enrichment

The standalone AbuseIPDB and VirusTotal enrichment apps are deprecated and will be removed in June 2026. Their replacement is Security Enrichment Security Enrichment, which provides all the same enrichment capabilities through vendor blueprint connections, along with response mapping, connection sharing, and workflow integration.

What will change: After the grace period ends in June 2026, the native AbuseIPDB and VirusTotal apps will be removed, and existing native connections will stop working. In-app deprecation banners guide you through the migration.

Action plan: Migrate each connection to Security Enrichment Security Enrichment using the vendor blueprint:

  1. Go to Security Enrichment Security Enrichment and select New connection.
  2. Choose the AbuseIPDB or VirusTotal blueprint.
  3. Enter your API key and optionally configure sharing.
  4. Select Test connection with a sample IP to verify the configuration.
  5. Save the connection.
  6. Remove the old native connection from the deprecated app.

Migration takes approximately 2 minutes per connection.

Infrastructure Observability

Network device extensions recommended feature sets and minimal default feature set

The new default feature set for network devices includes only interface status and control plane metrics. The interface traffic, discards, and errors metrics are now available under Interfaces and are no longer part of the default feature set. Metrics in the default feature set can't be unselected directly. However, interface filters can be set to remove the entire interface collection.
The recommended label is assigned to a few feature sets that provide enhanced observability on top of the default feature set. The metrics part of these recommended feature sets is selected by default and can be unselected. For more information, see Best practices for optimizing network monitoring cost.

Infrastructure Observability | Infrastructure & Operations

ActiveGate token management API for Latest Dynatrace

A new REST API for managing ActiveGate tokens is now available for Latest Dynatrace.

Platform | Dashboards

Stricter validation for dashboards

Starting with Dynatrace version 1.342, Dynatrace will apply stricter validation rules to dashboards and won't display dashboards that fail validation.

Who this affects: This will mainly affect dashboards created or modified via the API or external AI tools. Dashboards created and maintained using Dashboards Dashboards can’t fail validation unless you modify them otherwise.

  • If a dashboard fails validation before Dynatrace version 1.342, Dashboards Dashboards will display a warning and a failure reason, but the dashboard will continue to load as usual.
  • Starting with Dynatrace version 1.342, a dashboard that fails validation won’t load until you fix it.

Action plan: If you want to continue using a dashboard that failed validation, you need to fix it before Dynatrace version 1.342.

  • To fix a dashboard that failed validation, use the integrated JSON editor.
  • Read‑only dashboards that fail validation must be fixed by the dashboard owner.

Use Edit JSON to update the dashboard.

  • To edit directly in the Edit JSON editor, display the dashboard, select Edit JSON from the dashboard menu, make your changes, and then select Save. The editor will close, and your changes will be reflected in the dashboard.
  • To use a different editing environment, select Copy JSON in the upper-right corner of the editor to copy all of the JSON, and then paste the JSON into your own editor. After you make your updates in the other editor, copy and paste the edited JSON back into the Edit JSON editor and select Save.

Platform | Dashboards

Hidden single-select and multi-select variables no longer support default values

Hidden multi-select variables now always resolve to * (all options), and hidden single-select variables resolve to the first available value from the query results. This removes inconsistent behavior in which hidden variables that depend on visible variables can produce unpredictable values. If you previously relied on a static default value for a hidden select variable, use a text variable instead.

Fixes and maintenance

Resolved issues in this release (SaaS)

  • Fixed bug in the Oracle Insights View Statements page. (MGD-11991)
  • Fixed an issue where Kubernetes node monitored entities older than three years that had their names changed in Kubernetes (new) Kubernetes were not shown in Kubernetes Kubernetes Classic. (INFOBS-9874)
  • The apply commands for metric adapter deployment were updated for environments supporting Latest Dynatrace. For now, you need to manually generate a platform token with storage:buckets:read and storage:metrics:read permissions and paste it in place of the platformToken placeholder. (DEM-25874)
  • Fixed an issue within the Extensions Extensions (classic) where monitoring configurations could not be viewed or updated for extensions that were recently updated or installed. (DAQ-25128)
  • Extensions /monitoring-configurations endpoint now accepts only fully-formed semver version properties when creating a new monitoring configuration (DAQ-24971)
  • Improved consistency of database technology naming in filters. Db2 is now displayed using mixed case, aligning with IBM’s official naming convention.
    Possible low‑impact breaking change: If you rely on case‑sensitive filters, dashboards, or queries that reference the previous casing, you may need to update them. (OA-65544)
  • Resolved an issue where user email addresses were not updated correctly when a custom SAML email attribute was configured. The system now uses the configured SAML attribute value instead of the NameID. (MGD-11939)
  • Vulnerability: Enhanced Content Security Policy (CSP) by adding frame-ancestors and base-uri directives to improve protection against clickjacking and URL manipulation. (MGD-11137)
Related tags
Dynatrace Platform