What's new in Dynatrace SaaS version 1.312

Pre-release information

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

  • Release notes
  • 10min
  • Apr 8, 2025

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

Feature updates

Automations | SLOs

SLOs now support segments

The SLO definition now supports segments to either search for relevant entities or tailor the data considered for the SLI calculation.

  • Defining segments as part of an SLO allows you to tailor generic SLI definitions to the relevant data based on the segment definition.
  • Additionally, when visualized in a dashboard, the SLO takes a segment on the dashboard into account. This allows for a dynamic adjustment of the considered data points when evaluating an SLO.

Digital Experience | RUM Web

SRI for the RUM monitoring code

You can now leverage the subresource integrity (SRI) browser feature to ensure the integrity of the RUM monitoring code that is automatically injected or manually inserted into your web application.

Platform | Settings

New Settings page for external requests

The new and improved Settings page for external requests makes it even easier to allow outbound connections from AppEngine app functions and AppEngine ad-hoc functions.

You can find it in the Settings app under General in the Environment management group.

To learn more about the allowlist, see Allow external requests in the Dynatrace Developer documentation.

Digital Experience | RUM Web

Monitor and analyze Interaction to Next Paint (INP) with ease

Interaction to Next Paint (INP) has replaced FID (First Input Delay) among Google’s Core Web Vitals. As of now, Dynatrace offers the capability to monitor and analyze INP for the websites monitored by our customers.

While FID was used to measure the responsiveness of the initial interaction on a page, INP allows to assess the latency across interactions on a page.

In Dynatrace (Classic and Managed), customers can put our built-in INP metric (builtin:apps.web.interactionToNextPaint) on dashboards (Dashboards Classic) across various dimensions, such as frontend applications, browsers, and locations.

In addition, a user can assess INP values via accessing the frontend application overview screen as well as page analysis screens and filter for pages with the worst INP values to initiate improvements.

Frontend application overview including Interaction to Next Paint

Digital Experience | Synthetic

Added ephemeral storage limits to containerized location template

Containerized Synthetic location template now includes ephemeral storage requests and limits for each container.

Application Security | Security Investigator

Add context to your investigations with reference time

When analysing logs and events in Security Investigator Security Investigator, you can now use the reference time to keep track of the incident time and relative distance to it.

Setting the reference time will create a new virtual field for every timestamp field in your query results, which shows the time difference between the respective event time and the reference time you’ve defined.

Application Security | Vulnerabilities

Go support for RVA and RAP

Go technology is now available for Runtime Vulnerability Analytics (code-level vulnerability detection) and Runtime Application Protection (attack protection).

Action required

With this release, preview customers for Go technology (RVA and RAP) need to upgrade to OneAgent version 1.311 to reactivate this functionality. After that, no further configuration is necessary.

Breaking changes

Breaking change Dot Notebooks

Scopes removed from Notebooks

In this release, the following scopes are removed from the Notebooks Notebooks app:

  • davis-copilot:conversations:execute: Refer to the CoPilot chat available outside the app for general questions. Existing functionality to generate notebook section with Davis CoPilot is not affected by this change.
  • app-settings:objects:read: Internal scope, no workaround needed.

Please update your code sections accordingly. If you use code in your notebooks that relies on either of these scopes, this is a potential breaking change.

Upcoming changes

Kubernetes

Kubernetes dimension names change

The Kubernetes dimension names (dt.kubernetes.cluster.id, dt.kubernetes.workload.kind, dt.kubernetes.workload.name) won't be available starting with Dynatrace Operator version 1.7.

If you're still using them, update your configuration, queries, and other references to the new names as soon as possible.

Deprecated name
New name
dt.kubernetes.cluster.id
k8s.cluster.uid
dt.kubernetes.workload.kind
k8s.workload.kind
dt.kubernetes.workload.name
k8s.workload.name

Fixes and maintenance

  • Validation of DQL matcher queries in the classic log pipeline has been aligned with OpenPipeline, and incorrect queries in the form of matchesPhrase({attribute.name},"*") are no longer allowed. (PPX-4419)
  • Fixed an issue where, in premium HA environments, the connection to Elasticsearch was initialized with the wrong IP addresses. (MGD-3242)
  • Fixed an issue in the Calculated Service Metrics API that allowed the creation of unsupported metric "Capture full service call" (CAPTURED_FULL_SERVICE_CALLS). (APPOBS-5311)
  • Hardened potentially failing tenant startup when a RUM app name for the default application was written multiple times. (DEM-7053)

Dynatrace API

To learn about changes to the Dynatrace API in this release, check back here at GA.