What's new in Dynatrace SaaS 1.339

  • Release notes
  • 7-min read
  • Published May 07, 2026
  • Rollout start on May 19, 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.339. It contains:

Feature updates

Account Management | Subscriptions and Licensing

Improved process for purchasing Dynatrace Platform Subscriptions

Purchasing Dynatrace Platform Subscriptions via private offers on the Azure Marketplace is now easier. The updated interface and workflow let you synchronize your Dynatrace Platform Subscription start and end dates with your Azure SaaS, so contract periods match. You can also link multiple Entra IDs to your Dynatrace account. To do so, contact our support team and provide your Entra IDs.

For more information, see Azure Native Dynatrace Service.

Application Observability | Log Analytics

Log queries now run automatically when you open Logs from context

When you open Logs Logs from a dashboard, app, or other context, the log query runs automatically. You no longer need to select Run query to see log records.

Business Analytics | Business Analytics

Ingest up to 12 months of historical cost data

You can now ingest up to 12 months of historical cost data through monthly ingestion.

Digital Experience

Custom buckets for user.events and user.sessions tables

Real User Monitoring (RUM) now supports custom buckets for the user events table (user.events) and the user sessions table (user.sessions).

By default, RUM data is stored in the system default bucket for 35 days. You can optionally route subsets of RUM data into custom buckets using configuration rules. With custom buckets, you can control how your RUM data is stored:

  • Assign specific RUM data to dedicated buckets.
  • Configure custom retention and storage tiers per bucket. To leverage the extended retention, join the Extended Retention for RUM and Synthetic program.
  • Separate data for cost control, compliance, or team boundaries.

Digital Experience

End-to-end correlation between RUM and backend traces with W3C traceparent and tracestate headers

Frontend RUM agents (web and mobile) now set W3C traceparent and tracestate headers on outgoing requests, enabling end-to-end correlation between frontend sessions and backend traces in Grail. Web applications can enable header propagation for CORS requests via a new third-generation setting. Mobile agents support remote configuration and a manual linking API.

Digital Experience | Error Inspector

Error Inspector now uses Smartscape 2.0 entity data

Error Inspector now uses data from Smartscape 2.0.

Infrastructure Observability

Kubernetes Health Alerts, Warning Signals, and Custom Alerts

A new opt-in toggle lets you ingest most Kubernetes out-of-the-box alerts as warning signals instead of Davis problems. The toggle is off by default; when enabled, the events are classified as warnings rather than alerts wherever you query them—including in Kubernetes (new) Kubernetes. The Kubernetes anomaly detection settings page also has a refreshed look.

Infrastructure Observability | Clouds

GCP onboarding now lets you choose when to deploy Terraform

At step 3c of GCP onboarding, choose one of two options to finalize the flow:

  • Deploy Terraform now (default) — Deploy the downloaded Terraform, then wait up to 5 minutes for the service account to become ready. Select Finish to enable GCP monitoring configuration.
  • Deploy Terraform later — Select Finish to complete onboarding with monitoring configuration disabled. After you deploy the Terraform later, run the dtctl command shown in the UI to enable monitoring configuration.

Infrastructure Observability | Discovery & Coverage

Improved Host Coverage view in Discovery & Coverage app

We have updated the design of the Discovery & Coverage Discovery & Coverage Host Coverage page to improve the user experience, and added information on classic and new connections to help with upgrade.

Platform

Cloud and resource dimensions in OpenPipeline self‑monitoring metrics

OpenPipeline self-monitoring (SFM) metrics now include cloud and resource dimensions, so you can break down ingest by cloud provider and resource:

  • dt.sfm.openpipeline.ingest_sources_in.records
  • dt.sfm.openpipeline.routing.records
  • dt.sfm.openpipeline.pipelines_out.records
  • dt.sfm.openpipeline.not_stored.records

Added dimensions: cloud.provider, aws.region, azure.location, gcp.region, aws.resource.type, azure.resource.type, gcp.asset.type

Platform

Free-text support for non-entity filters in Data Explorer

The Filter by field in Data Explorer now accepts free-text input for non-entity filters. As you type, the free-text option appears with immediate feedback.

Platform | Dashboards

Get started faster with improved ready-made tiles and sections

Dashboards Dashboards and Notebooks Notebooks now come with a comprehensive library of ready-made tiles and sections. Each tile and section includes preconfigured visualizations and drill-downs into other apps, so you can go from zero to insight faster.

To access them, select in Dashboards Dashboards or Notebooks Notebooks, then scroll through the list or search for a specific ready-made tile or section.

Platform | DQL

More flexibility for pattern matching in DQL

DQL string patterns using the * wildcard character now support wildcards in the middle of a pattern. Previously, wildcards were only allowed at the beginning or end of a string pattern (for example, "*error*"). Additionally, the wildcard character itself can now be customized, enabling patterns that also match literal wildcard characters, for example: matchesPhrase(message, "a%/*", wildcard:"%").

This enhancement applies consistently across all string-matching functions and operators, including matchesValue(), matchesPhrase(), the search command, the ~ operator, field name patterns in field selection commands (for example, | fieldsKeep "dt.*.host"), Smartscape node and edge type selection, and Grail bucket name selection in fetch and timeseries commands.

Platform | OpenPipeline

Configure pipeline groups in OpenPipeline (Early Access)

You can now configure pipeline groups for OpenPipeline. This change allows you to create groups, manage their composition, and manage member stages and pipeline membership. To access the feature, go to OpenPipeline Settings.

Platform | Smartscape

Smarter, more complete topology views across Smartscape

Smartscape expands its hyperscaler coverage with a new Azure topology view, built on the newly released Azure cloud monitoring feature. This provides end-to-end visibility into your Azure infrastructure and its relationships. Additionally, all flat Smartscape views have been improved. Edges are now fetched using a smarter relevance-based logic that surfaces more of the connections that matter, and nodes are loaded according to a priority list to ensure the most important entities in your environment are always visible first.

Threat Observability | Security events

Checkmarx integration

Dynatrace now integrates with Checkmarx.

Breaking changes

Digital Experience | Synthetic

Deployment templates updated for Kubernetes and OpenShift synthetic locations

The synthetic private location and metric adapter deployment templates have been updated to support Latest Dynatrace environments. A new environment variable ,METRIC_3RD_GEN_ENABLED, enables the adapter to automatically select the appropriate API version based on your Dynatrace environment configuration.

For more information, see Containerized, auto-scalable private Synthetic locations on Kubernetes.

Fixes and maintenance

Resolved issues in this release (SaaS)

  • Fixed an issue where the Deep monitoring / Process group monitoring settings that deactivated monitoring were ignored for standalone/application-only and manually injected OneAgents. (PS-42728)
  • The functions isIpPublic, isIpPrivate, isIpLoopback, and isIpLinkLocal are now aligned with the RFC specifications. (GRAIL-50508)
  • The built-in view dt.davis.problems now also queries the built-in bucket default_davis_custom_events. (DI-27665)
  • Davis Events now correctly processes the incoming dt.openpipeline.pipelines field. (DI-26405)
  • Fixed an issue causing the RUM JavaScript to add headers to cross-origin requests if the base tag points to a different origin, triggering potentially broken preflight requests. (DEM-26180)
  • Fixed an issue resulting in consecutive visit generation if cookies cannot be set. (DEM-25392)
Related tags
Dynatrace Platform