Dynatrace SaaS release notes version 1.286

Rollout start: Feb 27, 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.

Breaking changes

Version 3.0.1 of Kubernetes connection settings schema deleted

Infrastructure Observability | Kubernetes

Version 3.0.1 of the Kubernetes connection settings schema (ID: builtin.cloud.kubernetes) has been removed, as it introduced a vulnerability that has been fixed in a subsequent release.

If you reference this exact version of the schema, you need to either change your integrations to reference a later version of the schema instead (the latest version is 3.1.0) or not reference the schema version at all (if it's not needed). See below for details.

With the Settings API, it's possible to specify this schema version for the following requests:

  • Fetching the definition of the schema for a specific version—with the schemaVersion query parameter GET api/v2/settings/schemas/builtin:cloud.kubernetes?schemaVersion=3.0.1
  • Creating a new settings object using version 3.0.1 of the schema definition—with the schemaVersion parameter of the JSON body POST api/v2/settings/objects with JSON body: 
    [
      {
        "schemaId": "builtin:cloud.kubernetes",
        "schemaVersion": "3.0.1",
        "scope": "KUBERNETES_CLUSTER-D3A3C5A146830A79",
        "value": {
          ...
        }
      }
    ]
  • Updating an existing settings object using PUT api/v2/settings/objects with JSON body: 
    {
      "updateToken": "<UPDATE-TOKEN>",
      "schemaVersion": "3.0.1",
      "value": {
        "enabled": true,
            "label": "test-cluster",
            "clusterIdEnabled": false,
            "endpointUrl": "http://some-example-url.org:12345",
            "authToken": "<AUTH-TOKEN>",
            "activeGateGroup": null,
            "certificateCheckEnabled": true,
            "hostnameVerificationEnabled": true
      }
    }

In each of these requests, the version parameter is optional.

If you have integrations that use any of these API calls with the schemaVersion parameter set to 3.0.1, they won't work anymore, because that specific version of the schema has been removed.

As stated earlier, to make your integrations work again, do one of the following:

  • Remove the schemaVersion parameter (if it's not needed)
  • Use another schemaVersion value (for example, 3.0.2 or 3.1.0)

Announcements

Let’s Encrypt certificate usage for Dynatrace SaaS

Platform Delivery | Certificates

Dynatrace has started to use Let’s Encrypt certificates for some components (for example, *.live.dynatrace.com).

For the majority of devices accessing Dynatrace SaaS, this has no impact.

In the past, however, Let’s Encrypt has had to replace a root certificate expiring in September 2021 (DST Root CA X3 replaced with ISRG Root X1). For details, see DST Root CA X3 Expiration (September 2021) - Let's Encrypt.

Although this new root certificate, ISRG Root X1, is trusted by every state-of-the-art device, it may not be trusted by very old devices, such as a device using an OpenSSL version earlier than 1.1.0 without the ISRG Root X1 certificate in the device’s trust store. These devices will fail to validate the certificate, for example, when accessing Dynatrace APIs from them.

Trusting the ISRG Root X1 certificate on these old devices resolves these issues.

For a list of devices/platforms from Let’s Encrypt that may be impacted, see Certificate Compatibility - Let's Encrypt

Deletion of legacy Kubernetes container metrics in Dynatrace version 1.292

Infrastructure Observability | Kubernetes

deprecated

In Dynatrace version 1.292, the following metric keys will be deleted, and access to their historical data will no longer be possible. If you are using any of these metrics, please migrate to the What to use instead metrics, which contain the same data and can be used to access the data.

Containers, CPU

Deprecated metric

What to use instead

builtin:containers.cpu.throttledMilliCores.legacy

  • Name: [Deprecated] Containers: CPU throttling, mCores
  • Description: CPU throttling per container in millicores. Deprecated metric for historical data access only.
  • Unit: Millicores
  • Aggregations: auto, avg, max, min

builtin:containers.cpu.throttledMilliCores

builtin:containers.cpu.usageMilliCores.legacy

  • Name: [Deprecated] Containers: CPU usage, mCores
  • Description: CPU usage per container in millicores. Deprecated metric for historical data access only.
  • Unit: Millicores
  • Aggregations: auto, avg, max, min

builtin:containers.cpu.usageMilliCores

builtin:containers.cpu.usagePercent.legacy

  • Name: [Deprecated] Containers: CPU usage, % of limit
  • Description: Percent CPU usage per container relative to CPU resource limit. Logical cores are used if CPU limit is not set. Deprecated metric for historical data access only.
  • Unit: Percent (%)
  • Aggregations: auto, avg

builtin:containers.cpu.usagePercent

builtin:containers.cpu.throttlingRatio

  • Name: [Deprecated] Containers: CPU throttling ratio
  • Description: CPU resource limit per container.
  • Unit: Ratio
  • Aggregations: auto, avg, max, min

There is no replacement for the throttling ratio, but it can be calculated on the fly from other metrics.

Memory

Deprecated metric

What to use instead

builtin:containers.memory.residentSetBytes.legacy

  • Name: [Deprecated] Containers: Memory usage, bytes
  • Description: Resident set size (Unix) or private working set size (Windows) per container in bytes. Deprecated metric for historical data access only.
  • Unit: Byte
  • Aggregations: auto, avg, max, min

builtin:containers.memory.residentSetBytes

builtin:containers.memory.usagePercent.legacy

  • Name: [Deprecated] Containers: Memory usage, % of limit
  • Description: Resident set size (Unix) or private working set size (Windows) per container in percent relative to container memory limit. If no limit is set, this equals total physical memory. Deprecated metric for historical data access only.
  • Unit: Percent (%)
  • Aggregations: auto, avg

builtin:containers.memory.usagePercent

New features and enhancements

Official support of Dynatrace Terraform Provider for configuration as code

Automations | Configuration as code

The Dynatrace Terraform Provider, enabling configuring Dynatrace environments as code using Terraform, is now officially supported and covered by the Dynatrace product support models.

New DQL functions

Platform | DQL

Now you can include the following function in your DQL queries:

Updated DQL functions

Platform | DQL

  • collectArray
    We added the expand parameter to the collectArray function.
  • collectDistinct
    We added the expand parameter to the collectDistinct function.

Detect unified services based on k8s.workload.name

Application Observability | Services

Unified-service detection rules evaluate the k8s.workload.name attribute. Services are detected first from k8s.workload.name, and then independently from dt.kubernetes.workload.name. Note: in the future, k8s.workload.name is planned to replace dt.kubernetes.workload.name.

Observability signals correlation for unified services

Application Observability | Services

We improved the correlation of metrics and logs to the related unified service so that metrics are no longer required to contain the service.name dimension.

Security data on Grail enhanced with entity change events

Application Security | Vulnerabilities

Security events now include entity change events. These are triggered whenever the status of the vulnerability (OPEN, CLOSE, REOPEN) is updated on the entity level.

For details, see Semantic Dictionary: Entity change events.

Improved exploration of logs and metrics

Latest Dynatrace Platform | Dashboards Platform | Notebooks We have made the following improvements for exploring logs and metrics in the Dashboards and Notebooks apps (Explore > Logs or Explore > Metrics):

  • The visualization interacts with, for example, Summarize, Convert to time series, and filter settings.
  • Results for logs are displayed immediately.
  • You can add and use multiple filters of the same kind (field).
  • You can remove any fields.

Dynatrace API

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

Dynatrace SaaS resolved issues

General Availability (Build 1.286.48)

The 1.286 GA release doesn't contain any user-facing resolved issues.

Update 54 (Build 1.286.54)

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

Update 64 (Build 1.286.64)

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

Update 67 (Build 1.286.67)

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

Update 70 (Build 1.286.70)

This cumulative update contains 9 resolved issues and all previously released updates for the 1.286 release.

Dynatrace Cluster

  • On the "Threat exposure template" created in Dashboards from the "Third-party vulnerabilities" page with the "Open with" button, data for the "Vulnerability count by risk level" tile is now displayed as expected. (SIA-2650)
  • Fixed a bug where new alerting profiles were assigned to existing problems, which could lead to unwanted assignments when the alerting profile configuration was not yet finished. (DI-7820)
  • Fixed a bug that caused high memory usage when reading availability data. (GRAIL-25063)
  • Fixed missing “Response time” column and chart data in the Topology card of the Service page. (TI-10960)
  • Fixed an error in VMware credentials disablement that occurred after five failed connections. (HOST-5121)
  • The alerting profile filter summary now shows the latest values for severity rules and event filters. (DI-7887)
  • In Data Explorer, selecting the "Open with" button no longer displays an error message when no error has occurred. (PAPA-9897)
  • The behavior of the "Monitor Kubernetes / OpenShift" deployment page is now dependent on whether network zones are enabled in the respective environment (see "Settings" > "Preferences" > "Network zones"). If network zones are disabled and the optional "Group" field on the deployment page is populated, the parameter `.spec.networkZone` is not set in the downloaded `dynakube.yaml` file, and this is explained in a warning message in the web UI. (K8S-9002)
  • Since SaaS 280, OS service events also match the tags from the host entity where they originate. This matching is now used for maintenance window evaluation. (DI-7907)

Update 76 (Build 1.286.76)

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