Dynatrace SaaS release notes version 1.292

Rollout start: May 21, 2024

What is new in Dynatrace

Want to ask questions or give feedback? Head over to What's New in Dynatrace in the Dynatrace Community.

Announcements

Metrics on Grail

Platform | Grail

Metrics on Grail is now in General availability. Metrics on Grail uses DQL to query metrics with the timeseries DQL command, allowing you to use metrics in conjunction with all the data in Grail, including logs and entities.

Metrics will continue to be written to both Classic and Grail storage to facilitate the transition from Metrics Classic to Dashboards and Notebooks.

The Metrics powered by Grail product category is introduced as part of the General Availability and available to DPS customers (Full rate card).

We're dropping support for IE 11

Starting with RUM JavaScript version 1.293, we will stop supporting Internet Explorer 11. For more information, see RUM JavaScript for Internet Explorer 11 and the related announcement in the Dynatrace Community.

Breaking changes

Maximum OpenTelemetry metric data points limit

Application Observability | OpenTelemetry

The OpenTelemetry protocol (OTLP) metrics ingest endpoint now enforces a maximum of 15 thousand metric data points per OTLP request. If the limit is exceeded, the endpoint returns a 413 Content Too Large response.

We recommend using a periodic metric reader in the OpenTelemetry SDK or a batch processor in the collector to limit the number of metric data points in the OTLP message.

New features and enhancements

Notebooks can be displayed in print view and exported to PDF

Platform | Notebooks

In Notebooks, you can now display a notebook in printable format. This also allows you to export a notebook to PDF. For details, see Print or export to PDF.

Explore metrics displays entity names by default

Platform | Notebooks Platform | Dashboards

In Notebooks and Dashboards, when exploring metrics and splitting by a dt.entity.*, the entity name (instead of the ID) is now displayed by default. The default limit for splittings is now 20.

Reduced DQL error level when querying non-existing monitored entities

Platform | DQL

A DQL query referencing a non-existing monitored entity no longer fails during verification of the statement or during query runtime. Querying a non-existing entity will now lead to an empty result.

Public internet exposure in limited monitoring modes

Application Security | Vulnerabilities

Dynatrace can now detect public internet exposure on Linux hosts running in Infrastructure Monitoring mode and Discovery mode via eBPF. Potential states are Public network and Not detected.

Removal of unused ActiveGate module attribute

Infrastructure Observability | Kubernetes

The KUBERNETES_AUTOMATIC_API_MONITORING attribute has been removed from the ActiveGate API response.

Deprecated container metrics

Infrastructure Observability | Kubernetes

The following container metrics have been deprecated:

  • builtin:containers.cpu.throttledMilliCores.legacy
  • builtin:containers.cpu.usageMilliCores.legacy
  • builtin:containers.cpu.usagePercent.legacy
  • builtin:containers.cpu.throttlingRatio
  • builtin:containers.memory.residentSetBytes.legacy
  • builtin:containers.memory.usagePercent.legacy

Process connection error event handling

Platform | Problems

Process connection error events will now merge into the same problem when occurring on the same host.

Wildcards in custom log sources

Infrastructure Observability | Logs

You can expand wildcards in custom log sources.

Introducing backward-incompatible changes to the builtin:logmonitoring.custom-log-source-settings schema

If you are writing the builtin:logmonitoring.custom-log-source-settings settings via API, you need to adjust them to the new schema, or specify the previous schema version, 1.0.6.

Dynatrace API

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

Dynatrace SaaS resolved issues

General Availability (Build 1.292.25)

The 1.292 GA release contains 10 resolved issues.

Component
Resolved issues
1
8
1

Application Security

  • Fixed the generation of the next page key when filtering security problems using management zones and sorting the results in descending order. (RSA-15138)

Dynatrace Cluster

  • When conducting root cause analysis for a slowdown, events that represent a generic kind of performance change (for example, `PERFORMANCE_EVENT`) are now also considered. This can lead to more findings in slowdown problems and merging slowdown problems with problems that contain performance events. (DI-14269)
  • Extension configuration statuses are no longer stuck in the loading state. (EXT-9986)
  • Changed root cause analysis to allow looking slightly into the future of the start of an event to account for data fuzziness. This should improve, for example, high memory on host events, to lead to high memory on process metric changepoints being found, because it allows for more context when looking for the changepoint. (DI-14261)
  • Fixed an issue that could temporarily prevent certain settings pages from working correctly on newly created environments. (PS-22946)
  • A DQL query referencing a non-existing monitored entity, no longer fails both during verification of the statement as well as during query runtime. Querying a non-existing entity will now lead to an empty result. (GRAIL-25967)
  • Enrichment logic that could cause Kubernetes service entity duplication was fixed. (K8S-9927)
  • Fixed enrichment of Kubernetes logs ingested using OneAgent: missing `k8s.cluster.name` attribute is now being added. (LOG-7267)
  • On the "Logs and events" page, updated the description of capabilities. (LOG-6940)

User interface

  • Fixed the way a log query is generated on entity pages. Correct logs are displayed for services pages after applying multiple filters on the same attribute. (LOG-6950)

Update 29 (Build 1.292.29)

This is a cumulative update that contains all previously released updates for the 1.292 release.

Update 32 (Build 1.292.32)

This cumulative update contains 4 resolved issues and all previously released updates for the 1.292 release.

Dynatrace Cluster

  • Fixed an issue that could temporarily prevent certain settings pages from working correctly on newly created environments. (PS-22946)
  • Enrichment logic that could cause Kubernetes service entity duplication was fixed. (K8S-9927)
  • Fixed an issue with user session queries containing the DATETIME function combined with MEDIAN, PERCENTILES, or COUNT(DISTINCT) functions. (GRAIL-28503)
  • Fixed enrichment of Kubernetes logs ingested using OneAgent: missing `k8s.cluster.name` attribute is now being added. (LOG-7267)

Update 40 (Build 1.292.40)

This is a cumulative update that contains all previously released updates for the 1.292 release.