Dynatrace Managed release notes version 1.220

These release notes relate to Dynatrace Managed specific changes. To learn about general Dynatrace changes included in this Dynatrace Managed release, see:

New features and enhancements

General

  • To take advantage of performance improvements, the latest security-vulnerability enhancements, and bug fixes, we've upgraded the following cluster node components:
    • Cassandra and Elasticsearch will now use JRE 8u292
    • Elasticsearch engine is now based on version 7.10
    • Other components will now use JRE 11.0.11
  • Dynatrace Managed is now also supported on:
    • Red Hat Enterprise Linux 8.4
    • CentOS 8.4
    • Oracle Linux 8.4
    • Ubuntu 21.04

For more information, see Dynatrace Managed system requirements.

Cluster Management Console

  • Managing permissions of tens, dozens, or hundreds of environments can be challenging. To increase usability experience in configuring granular cluster permissions, we've improved the Groups overview page. The table got simplified and was enriched with advanced filtering capabilities. You can now build an advanced filter based on:
    • Group name with any comparator of {contains, starts with, equals}
    • Permissions included in an environment, a management zone, any environment or management zone, a cluster, or an account
    • LDAP group name

See an example below:

Advanced filtering for groups overview

  • We continue to further enhance security by easily automating your API token protection. In this release, we're proceeding with earlier announced change and it's no longer possible to reveal generated token values in the Edit panel once those values have been saved. Remember to store the token in a safe place like a password manager, secret vault, or other password protection services. See the screenshot below, how improved Token Management UI looks like:

Copy token on creation

Token value no longer available

Operating systems support

Future Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 July 2025
The following operating systems will no longer be supported starting 01 December 2025

Completed product ideas

Resolved issues

General Availability (Build 1.220.96)

The 1.220 GA release contains 47 resolved issues (including 2 vulnerability resolutions).

Cloud automation solution

  • Resolved issue in which having two metrics with different entity types in an SLO resulted in being unable to evaluate the SLO. (APM-305867)

Cluster

  • Vulnerability: URL parameters that under certain circumstances were not masked at storage but are masked at display, will be masked according to user permissions. (APM-307314)
  • Vulnerability: URL parameters that under certain circumstances were not masked at storage but are masked at display, will be masked according to user permissions. (APM-307314)
  • Fixed an issue that caused some problems not to merge. (APM-298708)
  • Resolved issue in which activity infographic text for including extended users always showed `sessions` instead of `devices`, `browsers`, or `applications`. (APM-282129)
  • Fixed payload validation for maintenance windows for OneAgents in request to OneAgent auto-update public API. (APM-302186)
  • Resolved issue in which a relationship between a Kubernetes workload and a service was not properly set if multiple workloads related to the same process group. (APM-304483)
  • Data explorer improved to allow sharing a link with a timeframe greater than `Last 24 hours`. (APM-306260)
  • Fixed issue in which service metrics with multiple value conditions did not fetch data. (APM-305663)
  • Mapping for IIB node types has been updated. Resolves issue with request attribute configuration. (APM-304970)
  • Web vitals are no longer displayed for custom actions in the user session waterfall. (APM-280315)
  • Fixed issues with the RUM Web application configuration API. (APM-304841)
  • Fixed a bug related to writing time series for RUM metrics. (APM-305386)
  • Fixed classification of first-party and third-party requests for subdomains on the browser monitor analysis page. (APM-303100)
  • Resolved issue that could cause problem reporting failure. (APM-306813)
  • Fixed an issue that was preventing problem notifications from being sent out during cluster upgrade. (APM-301037)
  • Fixed issue with rounding decimal values for currently consumed host units on `Deployment status` page for OneAgent. (APM-305227)
  • The `extensionId` and `endpointId` fields of `ExtensionConfigurationDto` are now properly set. (APM-300262)
  • Fixed issue with Windows services availability monitoring settings where lower-level settings (at the host or host group level) override parent settings instead of extending them. (APM-301364)
  • Fixed an issue causing unrelated problems to merge. (APM-309278)
  • Added additional comparison parameter for request attributes: now they can be correctly distinguished from each other and therefore get correct IDs. (APM-306797)
  • Fixed potential problems with process group instance count violations that sometimes did not close when corresponding PGIs transitioned to an available state. (APM-305716)
  • Fixed an error condition that occurred in top list and pie chart tiles when the last dimension value was null. (APM-307197)
  • Constraint violations removed: entityId can now be changed; calculated service metrics can now also be created with "entityId" field via PUT request. (APM-306878)
  • Resolved issue with last value transformation of single value visualization. (APM-302910)
  • Fixed an issue where the root cause analysis would cause problems not to trigger notifications. (APM-305440)
  • Auto-update API no longer allows changing configuration and triggering update jobs for containerized ActiveGates. (APM-303382)
  • Incremented the size of the chart in Browser section of the session list page. (APM-303004)
  • Dimensions remainders are shown as REMAINDER instead of metric name. (APM-299723)
  • View change information is now masked in user sessions. (APM-306296)
  • Added `warnings` field to response of Timeseries API v1. Aligned permissions concept for all custom metrics: storing metric metadata requires `SettingsWrite` or `WriteConfig` permission. (APM-303016)
  • Fixed multidimensional analysis filtering on sensitive web request URL content with management-zone-only permissions. (APM-300339)
  • Data explorer improved to allow sharing a link with a timeframe greater than `Last 24 hours`. (APM-306260)
  • Resolved issue that could cause problem reporting failure. (APM-306813)
  • Fixed an issue causing unrelated problems to merge. (APM-309278)
  • Added additional comparison parameter for request attributes: now they can be correctly distinguished from each other and therefore get correct IDs. (APM-306797)
  • Constraint violations removed: entityId can now be changed; calculated service metrics can now also be created with "entityId" field via PUT request. (APM-306878)
  • View change information is now masked in user sessions. (APM-306296)
  • Fixed an error condition that occurred in top list and pie chart tiles when the last dimension value was null. (APM-307197)

Cluster Management Console

  • Resolved issues with display of user name and email when signed in with LDAP or SSO. (APM-303445)
  • Messages "Elasticsearch status verification failed." were limited to cases where upgrade really failed and required additional attention. (APM-310130)
  • Resolved issue with JRE security settings in Remote Access process. (APM-306618)
  • Resolved issue with JRE security settings in Remote Access process. (APM-306618)
  • Messages "Elasticsearch status verification failed." were limited to cases where upgrade really failed and required additional attention. (APM-310130)

Infrastructure monitoring solution

  • Changed message from `Could not find specified extension version` to `Schema for extension %s does not exist` if extension schema is not found. (APM-302868)
  • Fixed issue in which no metric data was shown if the selected management zone included a generic entity type filter. (APM-304534)
  • Fixed issue in which no metric data was shown if the selected management zone included a generic entity type filter. (APM-304534)

Update 112 (Build 1.220.112)

This cumulative update contains 6 resolved issues (including 1 vulnerability resolution) and all previously released updates for the 1.220 release.

ComponentResolved issues
Cluster4 (1 vulnerability)
Cluster Management Console1
RUM1

Cluster

  • Vulnerability: Enhanced access control in token creation. (APM-330727)
  • Fixed an issue with encoding `actionName` in RUM JavaScript API (colon was replaced with "^s"). (APM-312109)
  • Multiple v2 REST APIs: resolved issue in which incorrect handling of special characters in `nextPageKey` caused an `Invalid pagination key` error. (APM-313173)
  • Resolved issue in which DDU pool was not disabled/re-enabled, and notification was not updated, if pool limit was configured and consumption was greater than 21,474,836.47 in limit timeframe (month/year). (APM-314053)

Cluster Management Console

  • Notification email about an available server upgrade is now sent only once for each version, even if it couldn't be sent to some recipients on the list. (APM-311851)

RUM

  • Fixed an issue in which navigation from a dashboard to the Data explorer resulted in a 400 error. (APM-310542)