Dynatrace SaaS release notes version 1.270

Rollout start: Jul 4, 2023

What is new in Dynatrace

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

Product news

  • Automate predictive capacity management with Davis AI for Workflows

    >> Scroll down to see predictive capacity management in action (14-second video) Our recent blog post, Stay ahead of the game: Forecast IT capacity with Dynatrace Grail and Davis AI, showed how Dynatrace Notebooks are used to predict the future behavior of time series data stored in Grail™. This follow-up post introduces Davis® AI for […]

  • OpenTelemetry logs in Grail unlock full observability

    Dynatrace now offers native support for OpenTelemetry logs, which opens up the ability to collect all your observability data in a single platform and benefit from unified observability with other OpenTelemetry signals. This complements existing Dynatrace support for collecting traces and metrics via OpenTelemetry Protocol (OTLP) and allows you to get actionable answers from log data with the powerful combination of Grail and Dynatrace Query Language.

Announcements

Custom charts - end of support

  • What:

    If you depend on custom charts, you need to upgrade them now.

    • Custom charts no longer receive fixes and enhancements.
    • Custom charts are no longer editable.

    When you upgrade your custom charts to Data Explorer charts, you can edit your charts benefit from fixes and enhancements to Data Explorer features, and be ready to upgrade to the new platform.

  • When:

    • Dynatrace version 1.265 was the last Dynatrace release to support custom charts
    • Dynatrace SaaS version 1.271+ and Dynatrace Managed version 1.272+ completely disable custom chart editing and discontinue custom chart code maintenance

  • How:

    You can upgrade tile by tile, dashboard by dashboard, or, using the API, all at once.

For details, see Upgrade your custom charts now.

New features and enhancements

Access to Application Security notification settings

Application Security | Vulnerabilities

The following settings pages are now visible to users who don't have the Manage security problems permission, but only the View security problems permission:

  • Settings > Integration > Security notifications
  • Settings > Alerting > Vulnerability alerting profiles
  • Settings > Alerting > Attack alerting profiles

For more information on Application Security permission management, see Fine-tune permissions.

Hidden bulk changes in view-only mode

Application Security | Vulnerabilities

Bulk changes on Third-party vulnerabilities, Code-level vulnerabilities, and the remediation tracking page for process groups aren't visible to users with view-only access anymore. The Manage security problems permission is required to view and perform bulk changes.

For more information on Application Security permission management, see Fine-tune permissions.

New CyberArk authentication method for credential synchronization

Digital Experience | Synthetic Monitoring

A new method of authenticating with CyberArk Vault for credential synchronization allows you to use the hostname or IP address of a private or public Synthetic location—the hostname or IP address should have already been registered in the CyberArk Allowed Machines list.

When setting up a credential synchronized with CyberArk Vault, select Allowed machines (location) as the Authentication method. You need to register the hostname or IP address of your selected Location for synchronization in the CyberArk Allowed Machines list.

This authentication method bypasses the need for fetching a token from CyberArk. The resulting autocreated synchronization monitor contains a single GET request for fetching the synchronized credential.

Renamed monitor workload resource metrics toggle

Infrastructure Monitoring | Kubernetes

Monitor workload resource metrics toggle on monitoring setting page is now labeled as Monitor workload and node resource metrics.

Kubernetes conditions attribute table

Infrastructure Monitoring | Kubernetes

The Updated column in the Conditions table for node and workload pages now displays time in a relative format.

Extended important events list

Infrastructure Monitoring | Kubernetes

The Include important events toggle on Monitoring settings page has been extended to include four additional event reasons.

  • Preempting
  • BackoffLimitExceeded
  • DeadlineExceeded
  • PodFailurePolicy

Extended list of node conditions for alerting

Infrastructure Monitoring | Kubernetes

The Kubernetes out-of-the-box alert Problematic node condition has been expanded to include additional node conditions.

  • KernelDeadlock
  • ReadonlyFilesystem
  • FrequentKubeletRestart
  • FrequentDockerRestart
  • FrequentContainerdRestart
  • KubeletUnhealthy
  • ContainerRuntimeUnhealthy

Global default Kubernetes monitoring settings

Infrastructure Monitoring | Kubernetes

You can now configure default monitoring settings for Kubernetes, which will be automatically applied to all new Kubernetes clusters. For more information on default settings, see Global default monitoring settings for Kubernetes/OpenShift.

The Kubernetes monitoring settings have been split in two separate settings schemas:

  • builtin:cloud.kubernetes for connection settings
  • builtin:cloud.kubernetes.monitoring for monitoring settings

To prevent any incompatibility issues when configuring Kubernetes settings via the Settings API, update your API calls to align with the new schema. Alternatively, you can use the schemaVersion parameter to specify an older schema.

Dashboard filter logic improved

Cross Solutions | Dashboards

The logic behind user-defined custom dimension filters has been improved to eliminate extraneous results. For details, see Add dynamic filters to a Dynatrace dashboard.

Dynatrace API

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

Resolved issues

General Availability (Build 1.270.86)

The 1.270 GA release contains 5 resolved issues.

Component
Resolved issues
2
1
1
1

Autonomous Cloud

  • The dynakube.yaml download button for the Kubernetes/OpenShift deployment on the Dynatrace Platform now works in Firefox and Safari. (K8S-5879)
  • Corrected a Deployment page reference to point to the newly released Dynatrace Operator v0.12.0. (K8S-6202)

Storage

  • Disabled a new method of reading permissions optimized for large numbers of monitored entities because it caused performance problems for some deployments. (CLUSTER-7080)

Cluster

  • The `OSI_LOW_DISK_SPACE` event is now correctly highlighted. (HOST-3041)

NGINX

  • NGINX instrumentation has been updated for currency with NGINX 1.25. (OA-17247)

Update 88 (Build 1.270.88)

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

Update 90 (Build 1.270.90)

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

Update 92 (Build 1.270.92)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.270 release.

User Interface

  • Corrected an issue in which opening an entity (such as a service) in a new tab sometimes would instead open the main web UI page. (UIP-4109)

Update 96 (Build 1.270.96)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.270 release.

managed

  • Fixed an issue where Replay Session Data was enabled in all of our user groups of the cluster. (CLD-7287)

Update 98 (Build 1.270.98)

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

Update 104 (Build 1.270.104)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.270 release.

ActiveGate

  • OTLP Logs with empty body content (unset/null or empty) are now allowed and ingested into Dynatrace. (LOG-4085)

Update 110 (Build 1.270.110)

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