Dynatrace SaaS release notes version 1.300

Rollout start: Sep 9, 2024

New features and enhancements

Create custom start pages with launchpads

Platform | Launchpads

You can now build tailor-made start pages in Dynatrace using launchpads.

Launchpads let you keep everything you need in one place: create your personal launchpad with everything important to you, create a shared space for your project, and much more.

To get started

In the Launcher app, select Launchpad to add a new launchpad.
Select Customize.
Select a component type and start customizing it. Components you can add to your launchpad include:
- Links—A collection of links to Dynatrace apps and documents, as well as general links to internal or external resources.
- Markdown—A tile of Markdown-formatted text, including links to web pages and images
- Cards—For each card, add a brief explanation, an optional image, and a button to take you to your destination
After you have built your launchpad, select Done.

For details, see Launchpads.

Anomaly detection baselining, metric events, and availability

Platform | Davis

The following semantic dictionary fields are now enriched best-effort on Grail Davis events/problems for anomaly detection baselining, metric events, and availability:

cloud.region
cloud.provider
k8s.cluster.uid
k8s.cluster.name
k8s.namespace.name
k8s.workload.name
k8s.workload.kind
k8s.service.name
k8s.pod.name
k8s.container.name

The k8s.cluster.uid, k8s.cluster.name, and k8s.namespace.name fields are also available for Classic Events (exposed in events/problems v2 REST, notifications).

Dashboards and Notebooks: improved filtering

Platform | Dashboards Platform | Notebooks

Explore sections and tiles for logs, metrics, and business events now offer an improved type-ahead filter experience based on the new filter field component. Improvements include the ability to use logical operators (AND, OR) directly in the web UI, a simplified filtering syntax, or value suggestions for metrics as well as entity field suggestions for logs.

OpenTelemetry metrics ingest API now accepts histograms

Application Observability | OpenTelemetry

The OpenTelemetry metrics ingest API now accepts histograms.

By default, Gauge metrics for both explicit and exponential histograms will be ingested.
Buckets from explicit histograms are opt-in. To enable this, go to Settings > Metrics > Histograms.
For now, buckets from exponential histograms are not accepted.

Dynatrace API

To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.300.

Dynatrace SaaS resolved issues

General Availability (Build 1.300.26)

The 1.300 GA release contains 13 resolved issues.

Component	Resolved issues
Dynatrace Cluster	11
Session Replay	2

Dynatrace Cluster

Disk options settings are available in Discovery mode. (OA-34186)
OneAgent diagnostics: when you generate a support archive, an inaccessible Health Control link is no longer displayed. (Link is displayed for internal access only). (TI-13932)
Fixed a case where two problems referred to each other as duplicates when one of the problems should have been the main one. (DI-15839)
Fixed empty event titles for informational Davis events that have an end time already at creation. (DI-15999)
Fixed an issue in which, for premium high availability Managed clusters, after a data center failover, problems created during the failover period were not manually closeable. (DI-15087)
Fixed billing for certain metrics that were overbilled with the DPS licensing model. (GRAIL-32358)
Fixed an issue in which, when requesting the details for a specific update job for a particular ActiveGate via the "GET an auto-update job" endpoint, a 404 error was returned if the job was older than 7 days, even though the maximum requested timeframe is for the last 31 days. (DMX-8235)
A client IP hint is no longer shown if no client IP is available. (TI-13978)
Fixed an issue that could result in a broken remote environment integration link in the service overview. (TI-13948)
Fixed broken remote environment integration links in service overview and trace view when "Latest Dynatrace" is enabled. (TI-13976)
The mobile OS version is now displayed correctly in sessions for hybrid apps. (RUM-21070)