Dynatrace Managed release notes version 1.270

  • Release notes
  • Published Jul 12, 2023

Rollout start: Jul 12, 2023

Announcements

Internal components upgrade

The upgrade from version 1.268 to version 1.270 includes upgrades of internal components of the Dynatrace Managed product: JREs, Elasticsearch, and Cassandra.

  • If Automatic Upgrade is enabled, changes are already included in the upgrade procedure. No action is required.

  • If you perform an upgrade manually from a command line, be sure to read 268 to 270 release procedure for Managed clusters in the Dynatrace Community.

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 very soon will not be editable.

    When you upgrade your custom charts to Data Explorer charts, you will be able to edit your charts and you will benefit from ongoing fixes and enhancements to Data Explorer features.

  • When:

    • Dynatrace Managed version 1.266 was the last Dynatrace release to support custom charts
    • The next release, 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

Entry point information for code-level vulnerabilities

Application Security | Vulnerabilities

To help you get to the source of a code-level vulnerability and determine exactly what is needed to resolve it, entry point information is now displayed on the details page of the vulnerability. For details, see Entry points.

Additional events in vulnerability evolution

Application Security | Vulnerabilities

Vulnerability evolution now shows these events:

  • Davis Security Score changed
  • CVSS Score changed
  • Risk assessment changed
  • Number of reachable data assets
  • Public internet exposure
  • Public exploit available
  • Vulnerable function usage
  • The number of affected process groups changed
  • The number of affected nodes changed (only for Kubernetes vulnerabilities)
  • Attacks detected (only code-level vulnerabilities)

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.

Init container support

Infrastructure Monitoring | Kubernetes

We added parsing of the init containers. The following metrics now include occurrences of initContainer; therefore, you might experience an increase in numbers there.

  • builtin:kubernetes.container.oom_kills
  • builtin:kubernetes.container.restarts

Additionally, names of init containers now appear in the values of the k8s.container.name dimension and in log lines.

New design of service and database overview pages

Apps & Microservices | Distributed traces

The unified analysis page framework is now available for the service and database pages. The new design supports faster troubleshooting with fewer steps:

  • Interactive microcharts that add focus on suspicious patterns
  • (Key) Requests directly on the overview page
  • Davis exploratory analysis
  • Traces, logs, service metrics, and SLOs in context
  • Improved topology visualization

To switch to the new design, turn on Try it out at the top of the overview page. To revert to the classic design, select More (…) > Return to classic page on the overview page.

Share your feedback in the Feedback channel for the new opt-in OneAgent and DB services’ pages - v1.269 (SaaS), v1.270 (Managed) in the Dynatrace Community.

New design of service and database overview pages

OTLP logs ingest endpoint

OpenTelemetry

You can now ingest OpenTelemetry logs using the OpenTelemetry Protocol (OTLP) as a binary Protobuf over HTTP.

For more information, see:

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.

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:

Operating systems support

  • Added support for Oracle Linux 8.8
  • Added support for Red Hat Enterprise Linux 9.2
  • Added support for Oracle Linux 9.2
  • Added support for Rocky Linux 9.2

    Future Dynatrace Managed operating systems support changes

    The following operating systems will no longer be supported starting 01 January 2026
    The following operating systems will no longer be supported starting 01 June 2026
    The following operating systems will no longer be supported starting 01 July 2026

    Past Dynatrace Managed operating systems support changes

    The following operating systems are no longer supported since 01 July 2025
    The following operating systems are no longer supported since 01 December 2025

    Resolved issues

    General Availability (Build 1.270.96)

    The 1.270 GA release contains 22 resolved issues.

    ComponentResolved issues
    Application Security2
    Autonomous Cloud2
    Cluster6
    Infrastructure monitoring solution1
    Managed1
    NGINX1
    Session Replay2
    Storage1
    Synthetic monitoring2
    User Interface2
    metric query2

    Application Security

    • Fixed an issue where in some cases, Application Security monitoring rules evaluation only considered the currently added/edited rule instead of all available rules, leading to a wrong monitoring state of entities and a wrong usage consumption. (RSA-10512)
    • Fixed an issue that caused the "Change status" button and the bulk muting confirmation button on the remediation tracking page to be disabled for users with partial management zone permissions. Buttons are now displayed as enabled, and the permission check is delegated to the API in case of partial management zone permissions. (RSA-10126)

    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)

    Cluster

    • The correct threshold is now reported when reporting problems resulting from metric events using the auto-adaptive baseline monitoring strategy. (The baseline/threshold given in the problem description was outdated. The alerts themselves were not affected and were correct.). (DAVIS-4848)
    • Fixed an issue that, in rare situations, caused a manually closed problem to reopen after a maintenance window had ended. (DAVIS-4765)
    • Fixed an issue where JavaScript agent build units could not be downloaded for newly created tenants on new clusters. (RUM-11774)
    • The filter field expression in VMware settings now accepts null values. (HOST-3011)
    • The `OSI_LOW_DISK_SPACE` event is now correctly highlighted. (HOST-3041)
    • Opening the multidimensional analysis from "Data explorer" when viewing a calculated service metric no longer requires calculated service metric configuration permissions. (TI-7076)

    Infrastructure monitoring solution

    • Corrected the aggregation type for the `builtin:host.dns.queryCount` and `builtin:host.dns.errorCount` metrics from AVG to SUM. (HOST-2992)

    Managed

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

    NGINX

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

    Session Replay

    • Fixed an issue where, in some situations, the replay became stuck with the "Loading Session Replay data" message displayed. (SR-2496)
    • Fixed an issue in which, when two or more Session Replay tabs were open, there was a mismatch in the HTML content. Each session is now shown properly. (SR-2192)

    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)

    Synthetic monitoring

    • Fixed an error related to the list of events included in the response body when retrieving the details of a Synthetic browser monitor using the API. (SYNTH-5176)
    • Improved data source handling in execution details to prevent exceptions that occurred in certain situations. (SYNTH-4751)

    User Interface

    • Improved generated access token presentation to only partially display the secret in the web UI by default; just the first public part is displayed in a single line input, not a multi-line text area. (UIP-3819)
    • 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)

    metric query

    • Fixed issue with missing dimensions for the metrics "Host availability %" and "Process availability %". (CLUSTER-7173)
    • Fixed negated metrics leading to errors on aggregation in metric selectors. (CLUSTER-6773)

    Update 110 (Build 1.270.110)

    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 130 (Build 1.270.130)

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

    datastax

    • Fixed a bug that caused internal database queries to fail during rolling restarts/updates when only one database node remains available in multi-node deployments. (CLUSTER-7874)

    Update 132 (Build 1.270.132)

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

    Managed

    • Fixed an issure where the user is not able to read permissions via the REST API. (CLD-7385)

    Update 140 (Build 1.270.140)

    This cumulative update contains 2 resolved issues and all previously released updates for the 1.270 release.

    Cluster

    • Fixed metrics malfunction when more than a certain threshold is created. (CLUSTER-7919)
    • Fixed an issue where no RUM JavaScript metadata has been found for an application. (RUM-12838)

    Update 150 (Build 1.270.150)

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