Dynatrace Inc.

06/02/2026 | Press release | Archived content

What’s new in Dynatrace SaaS version 1.340

  • Release notes
  • 10-min read
  • Rollout start on Jun 02, 2026

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

FinOps

Proactive Cost Intelligence across your entire stack

Use Dynatrace Cost Intelligence to understand your costs, act before they spike, and optimize with ease.

FinOps best practices

Managing and optimizing Dynatrace costs just got clearer. We've published new Optimize documentation that guides DPS customers through the full journey from understanding to optimizing costs, aligned with the FinOps Foundation framework.

Self-service usage and cost insights

We've introduced self-service usage and cost insights as a ready-made Usage - Overview dashboard to guide you from free trial to full deployment with a consistent experience.

If you're on a free trial, you can now see exactly how your usage maps to cost, so there are no surprises. As an existing customer, you get actionable insights with drilldowns to quickly identify cost spikes, root causes, and the teams responsible, accessible as ready-made Dashboards or out of Account Management.

Cost Intelligence for deep analytics and optimization

Use Dynatrace to understand, predict, and optimize usage, no further expertise required. Ask questions like:

Try: "I received a cost alert that costs have increased. Can you check if you find anything notable?"

What you'll get: A full drilldown into your events with the root cause surfaced directly-no manual exploration needed.

Try: "Based on my log ingest usage over the last 90 days, can you predict my next 30 days?"

What you'll get: A capability-level prediction based on your actual consumption, useful when onboarding new teams.

Try: "Looking at optimizing my log query usage-are there any queries duplicated by multiple users?"

What you'll get: Insights into overlapping queries with direct suggestions on how to improve.

Feature updates

Account Management | Cost Management

Maintenance of DDU consumption metering

Technical foundations for DDU consumption metering for classic licenses regarding Logs on Grail and Bizevents on Grail are reworked for maintenance reasons. The consumption logic itself does not change.

During the hour when this transition takes place, you may see a DDU consumption gap within a single billing hour affecting the following metrics:

Account Management | Subscriptions and Licensing

Single POD email for combined Amend & Extend subscription orders

You can now select the Amend and Extend POD template, so you can receive a single POD email containing both amended subscription changes and new renewal subscription terms.

AI Observability | AI Observability

Added Python support for GenAI services and frameworks

OneAgent version 1.339+ Dynatrace version 1.340+

OneAgent now provides automatic instrumentation for Python applications that use AWS Bedrock, OpenAI, Azure OpenAI, and LangChain.

  • Dynatrace captures distributed traces, logs, and GenAI-related telemetry for supported model interactions, including provider, operation, model, duration, token usage, and prompt and completion metadata where available.
  • You can capture prompt and completion content to debug AI and LLM interactions, analyze model behavior, and understand the performance and cost impact of calls to large language models. To enable it, go to OneAgent features and turn on Python OpenAI prompt capture [Opt-In].

Application Observability | Distributed Tracing

Investigate traces faster with clarity and navigation improvements in Distributed Tracing

Several enhancements make it easier to analyze and navigate trace data in Distributed Tracing.

  • Facet counts are now visible directly in the facets panel, so you can quickly grasp the distribution across different values without expanding individual filters.
  • A meter bar visualization in the duration column of the span list table lets you compare span durations at a glance.
  • You can now start Dynatrace Assist conversations directly from the trace Logs viewer.
  • New keyboard shortcuts speed up navigation: select S to jump to the search bar, select F to jump to the filter field.

Application Observability | Log Analytics

Log module self-monitoring enabled by default for Grail

The Dynatrace log module now emits self-monitoring events that deliver an environment-wide health overview for OneAgent and Kubernetes log modules. You can detect and resolve log ingest issues across distributed fleets faster, with self-service troubleshooting based on per-source status and health signals.

What's new:

  • Self-monitoring events for log module health and log source status, stored in Grail . Two event categories emitted: log source status and health-related events.
  • Troubleshooting guides covering each event type, with remediation steps and query examples.
  • Dashboard visualizing fleet health and detected log source status-available as a downloadable package from documentation or via the upgraded built-in Log ingest overview dashboard.
  • Suppression mechanism to disable specific event types per configuration scope.

Where to find it:

  • Events in Grail
  • Dashboard package
  • Troubleshooting guides in our documentation.

Enabled by default for Grail; available as opt-in for Log Monitoring Classic (LMv2).

Application Observability | Services

Explorer Preview with service map and primary Grail Fields filtering in Services app

Services now includes a visual service map that shows service-to-service relationships and messaging flows, with performance and health indicators overlaid on the topology. That makes it the fastest way to understand blast radius during an incident, with topology context, performance signals, and bottlenecks visible in a single view without switching views. You can also filter services directly by primary Grail fields such as , , , and ; the same attributes that power segments across Dynatrace.

Both capabilities are available in the ExplorerPreview view and are open for feedback before General Availability. For more details, see Community .

Digital Experience | Users & Sessions

Full-screen mode for Session Replay

You can now watch Session Replay in full-screen mode.

Infrastructure Observability | Infrastructure & Operations

Platform tokens for classic network zone APIs

Added support for platform tokens for classic network zone REST APIs.

Infrastructure Observability | Infrastructure & Operations

Platform tokens for classic ActiveGate APIs

Added support for platform tokens for classic ActiveGate REST APIs.

Infrastructure Observability | Infrastructure & Operations

Platform tokens for classic OneAgent APIs

Added support for platform tokens for classic OneAgent REST APIs.

Platform

What's New - now in-product

All product news right in the product-searchable, filterable, shareable.

  • Search across titles, descriptions, categories, and version numbers.
  • Filter by category-pick Logs, Dashboards, Application Observability, or any other product area with a single click.
  • Share easily-copy the URL to share entries with your peers.

Platform | Dashboards

In Dashboards and Notebooks, in the table visualization, the record details viewer now groups fields by main type. This includes primary tags and topology fields, as well as fields hidden by table column settings.

Platform | DQL

Durations now also support decimal numbers

Duration literals (h, m, s, ms, us, ns) now also support decimal numbers.
Examples:

  • -which is equal to the previously supported or

If sub-nano precision is used, decimals are cut off:

  • is always converted to , meaning that even , whereas . While technically supported, the decimal notation only makes sense for units greater than nanoseconds
  • will also be truncated to , ignoring everything after

Note:

This is only supported for durations, not for calendar durations.

  • Due to daylight saving time, is ambiguous and could be something between and . For , it becomes even more obvious.
  • As it is not supported for calendar durations, even isn't supported as literal-use instead.

Platform | Problems

Additional event REST endpoints

Environments created on or after January 26, 2026, can now access the and REST endpoints. These endpoints are needed to be able to correctly create the events ingest payload.

Platform | Smartscape

Locate specific nodes across any Smartscape view

You can now search for nodes by name or ID across all Smartscape views, including modal views. Press Ctrl+F (or Cmd+F on Mac) to focus the new search field-Dynatrace highlights matching nodes in the graph and narrows the legend to the matching entity groups. The legend is also interactive: expand any entity type to see its nodes and jump to them in the graph without typing a query.

Threat Observability | Security events

Checkmarx integration

Dynatrace now integrates with Checkmarx. For details, see Checkmarx Ingest .

Breaking changes

Infrastructure Observability | Infrastructure & Operations

Deprecation of ActiveGate auto-update API

The ActiveGate auto-update configuration API is deprecated. Instead, use the Settings 2.0 API with the schema ID.

Infrastructure Observability | Infrastructure & Operations

New REST API for host-based ActiveGate deployment

A new REST API is now available for deploying the ActiveGate installer and retrieving connection information. Unlike the classic API, this API supports non-preconfigured installers, enabling deployment without environment-specific preconfiguration.

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 cannot fail validation unless you modify them otherwise.

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.

Software Delivery | Ecosystem

Support for Smartscape topology on and

We added support for Smartscape topology on and .

Fixes and maintenance

Resolved issues in this release (SaaS)

Dynatrace Inc. published this content on June 02, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on June 10, 2026 at 06:29 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]