Dynatrace SaaS release notes version 1.259

Rollout start: Jan 31, 2023

Announcements

Davis Assistant end of life

Dynatrace Davis Assistant has reached end of life on January 31, 2023. For options and best practices on managing the push of problem notifications to your preferred third-party incident management or ChatOps service, see problem notifications documentation.

New features and enhancements

Log dashboards strategies

Infrastructure Monitoring | Log Management and Analytics

You can visualize data from your logs using dashboards. You can adjust dashboards to your observability needs, performance and consumption, by selecting one of the two strategies: pinning DQL queries or pinning log metrics.

For details, see Log dashboards strategies.

New metric for workload conditions

Infrastructure Monitoring | Kubernetes

A new built-in metric builtin:kuberntes.workload.conditions is added to Kubernetes API monitoring. It contains the actual conditions stated on Kubernetes workloads, such as Deployment and Cronjobs, and is structured similarly to the already existing node conditions metric.

Improved metric performance

Infrastructure Monitoring | Kubernetes

The builtin:containers.memory.usagePercent and builtin:containers.cpu.throttledMilliCores metrics now only hold data acquired starting with Dynatrace version 1.257+. To access historical data, use the corresponding legacy metrics.

Improved syntax for event field selector expressions

Infrastructure Monitoring | Kubernetes

There are new requirements for the field selector expression:

  • Both Key and Value are restricted in length.
  • Value is optional and can contain all characters except exclamation marks (!), equal signs (=), and commas (,).

For more information, see Set up event field selectors.

No Ports section if ports aren't defined

Infrastructure Monitoring | Kubernetes

If no ports are defined, the Ports section is no longer displayed on a Kubernetes service details page.

Azure Storage Account

Infrastructure Monitoring | Azure Service Monitoring

Dynatrace ingests metrics for multiple preselected namespaces, including Azure Storage Account. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.

For more information, see Azure Storage Account (Blob, File, Queue, Table) monitoring.

Dynatrace API

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

Resolved issues

General Availability (Build 1.259.283)

The 1.259 GA release contains 11 resolved issues.

Application Security

  • Improved robustness of the process group overview page (fixes an infrequent crash). (RSA-7551)

Cluster

  • Support for OAuth 2.0 in webhook problem notifications was recently added, but the new feature created an API breaking change by requiring a new property to be specified in POST requests to the Settings 2.0 API for the problem notifications schema. The property is now optional so as not to break API integrations with existing payloads. (DAVIS-3319)
  • On "Settings" > "Anomaly detection" pages, corrected descriptions of baselining settings (changed "average" to "median"). (DAVIS-3144)
  • Fixed an issue with opening host or process group instance details page that might lead to 500 error blocking access to those pages for customers which were using legacy log monitoring v1 with combination of events extraction functionality. (APM-393678)
  • Fixed an issue that, in certain cases (for example, availability events), caused events to merge with other events into a single problem even though they were configured not to merge. (DAVIS-3112)
  • Synthetic problems with different events now have a synthetic-related title. If a problem only consists of synthetic events, but no other application-level events such as application slowdown, we used to name the problem 'Multiple application problems'. This was unintended and should be 'Multiple synthetic problems'. Furthermore, when HTTP checks are failing locally and globally, we now merge those different events into a common problem titled 'Http monitor outage'. (DAVIS-3017)
  • Management zone handling on Kubernetes pages has been improved. Important note: To prevent displaying too much information on the cluster details page, you need to configure management zones correctly. The dimensional rule has to have the same scope as the entity rule. For example, if the management zone is filtered by a namespace, the entity rule and dimensional rule need to include a condition for that namespace. (K8S-4617)

metric ingest

  • When tracking the number of external data points (`dsfm:server.metrics.ingest.external_datapoints` and `dsfm:server.metrics.ingest.external_datapoints_by_source_address`), the data points of self-monitoring metrics are no longer taken into account. (CLUSTER-3999)

sepl server stream

  • Fixed injection status message in Web UI incorrectly stating that PHP 8.2 is not supported. OneAgent version 1.253+ is capable of injecting PHP 8.2. (CLUSTER-4013)

Autonomous Cloud

  • The "Monitor Kubernetes / OpenShift" deployment page now references the newly released Dynatrace Operator v0.10.2. (K8S-4484)

metric low-level

  • Fixed an issue when the Container Group instance metric queries can cause data loss by triggering ALR. (CLUSTER-4459)