Dynatrace Managed release notes version 1.224

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

  • You can now filter the Release inventory table (go to Releases) by the build version.

  • You can now filter the Release inventory table (go to Releases) by the technology type and version of the corresponding process group instances.

  • We have introduced a metric for Davis event ingestion.

  • Added support for filtering Data Explorer tiles on dashboards.

  • We improved security when loading custom chart tiles on a shared dashboard by moving query execution completely to the server to further reduce potential threat vectors.

  • The waterfall shows more hints if Core Web Vitals are not available.

  • We streamlined the dashboard tile editing process a little. When you are finished editing a tile, you have three choices:

    • Select Done just once to exit edit mode and display the finished dashboard. (Formerly, you had to select Done twice to finish editing the tile and then finish editing the dashboard.)
    • Select another tile to edit the selected tile.
    • Select in any empty area on the dashboard to display the tile catalog and dashboard settings.

  • We releases problems v2 API, see Dynatrace API changelog version 1.224.

  • It is now possible to set the stage of a release with the Kubernetes pod label 'dynatrace-release-stage'.

  • Kubernetes pages for namespace, workload and pod are extended with a breadcrumb navigation bar that shows the Kubernetes hierarchy from the cluster down to the pod level.

  • Service-level objectives (SLOs) now consist of a metric expression instead of either a metric rate or two metrics for good/total value. This introduces some changes in the web UI and SLO API.

  • We redesigned the "Define the SLO target" ("Set your target") step in the "Add new SLO" wizard to make it easier to define the service-level objective target and warning values.

  • We have updated the list of devices usable for browser monitors to include more current device models, and we have removed some outdated devices.

  • Dynatrace Managed is now also supported on Suse Linux Enterprise Server 15 SP3.

Resolved issues

General Availability (Build 1.224.74)

The 1.224 GA release contains 37 resolved issues (including 1 vulnerability resolution).

Component
Resolved issues
34
3 (1 vulnerability)

Cluster

  • Improved database service detection where no port is detected: if the candidate process group suggested by the topology has the technology of the database, it is associated with the database call; otherwise, it is associated only with the host. (APM-314790)
  • Corrected the link to documentation from user details (go to "Session segmentation" and select a user, and then select the "Learn more" link for the "Extended users..." switch). (APM-313905)
  • Web service name simplified to no longer contain host or process group information. (APM-315412)
  • Fixed migration to `Data explorer` for custom charts containing legacy plugin metrics. (APM-316472)
  • Fixed display names of legacy plugin metrics in custom charting. (APM-316469)
  • Fixed issue with long request time for `Host settings` > `Detected processes`. (APM-315254)
  • Fixed an issue with browser monitor breadcrumbs. (APM-313343)
  • On the user details page, the "Extended users..." switch is never disabled now if there is at least one extended user for the specified timeframe. (APM-314148)
  • Users in a management zone no longer get a 403 HTTP error when opening Kubernetes pages. (APM-324758)
  • Fixed an issue with mobile symbolication file storage to allow "unlimited" quota setting in Dynatrace Managed environments. (APM-312151)
  • Fixed an issue in which the displayed number of open problems differed between mobile app and web UI. (APM-314219)
  • The "User sessions" page, when "Analyze more data" is selected, no longer shows "0 results" when fetching intermediate data for user sessions after some data has been already fetched. (APM-296188)
  • Fixed an issue with read masking for pages. (APM-307851)
  • The "User sessions" > "Conversions vs bounces" chart now displays a tooltip on hover. (APM-312164)
  • URLs that are used only as additional information for Synthetic actions are no longer shortened. (APM-314301)
  • When license is expired, we provide now correct email in top bar. (APM-315761)
  • Calculated Service metrics API - passing null/empty as a value for the `metricDefinition` key parameter now returns an appropriate constraint violation message. (APM-313239)
  • Darwin is now recognised as an Apple OS. (APM-311621)
  • The number of affected Kubernetes nodes of the vulnerability details card now matches the number in the vulnerable components card. (CASP-10339)
  • Resolved issue in which the Visually Complete 2.0 algorithm was not activated automatically in some circumstances. (APM-312152)
  • The "Dashboards" page now displays the admin toggle only for admins and devops users. (APM-311677)
  • Fixed issue with missing timings for Synthetic user actions. (APM-313751)
  • Session list filters are no longer lost when changing filters on "Session details" page. (APM-313278)
  • The Session Replay tab on session details page is now also displayed for Synthetic users. (APM-307056)
  • On "User sessions" page, when a category from the side panel is applied, the "Return to sessions" link now correctly preserves global timeframe and filters. (APM-312363)
  • Honeycomb dashboard tiles (Host health, Service health, etc.) with filters and remote environment configured now have working drilldowns to the corresponding view on the remote tenant. (APM-313297)
  • Fixed an availability alerting bug related to evaluation of the host group and host settings when "Use global anomaly detection settings" was selected after editing host or host group settings. (APM-315121)
  • Added support for `UserAction` and `Session` properties of type LONG_STRING to Configuration API. (APM-315513)
  • Fixed a bug related to custom error rules in the RUM - Web application configuration API (null fields were not allowed in PUT request). (APM-311723)
  • Resolved issue in which navigation to problem details page sometimes resulted in 404 not found error. (APM-312975)
  • GWT error page analytics data is now sent when the error page is displayed. (APM-313545)
  • On the "User sessions" page, if a filter button would result in 0 matching items, the button is disabled. (APM-306087)
  • Fixed issue that caused unauthorized requests to the Synthetic Monitoring API to return unexpected error response. (APM-317625)
  • Added information on the self-enablement page about OneAgent release 1.217 requirement for Log Monitoring v2. (APM-319208)

Cluster Management Console

  • Vulnerability: Implemented hardening against server-side request forgery (SSRF) attack. (APM-307227)
  • Resolved issue with slow FedRAMP SSO IdP-initiated sign-in and error upon sign-out. (APM-310965)
  • Resolved issue that caused infinite dashboard page loading in certain circumstances when redirected from SSO sign-in for Managed clusters. (APM-316656)

Update 80 (Build 1.224.80)

This cumulative update contains 3 resolved issues and all previously released updates for the 1.224 release.

Cluster

  • To avoid high Cassandra Database loads, REST API calls are no longer audited. (APM-321322)
  • Resolved issue in which HTTP monitors using credentials did not receive a credential update when they were running on public locations, so that they used the old value for public location executions unless the monitors were updated specifically. (APM-320713)
  • Dashboard filters such as Kubernetes cluster, Kubernetes namespace, and Kubernetes workload are now properly applied to `Data explorer` tiles with built-in metrics. (APM-319031)

Update 84 (Build 1.224.84)

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

Cluster

  • Resolved issue in which, when a cluster node hit memory hard cleanup and stopped processing incoming user sessions data, it failed to start processing incoming user sessions data again when the cluster node returned to normal memory conditions. (APM-322680)
  • Resolved an issue in which, for some schemaless metrics sent via MINT API, data was lost. Affected: MINT metrics where the metric key was modified by Dynatrace on the cluster, including (1) count metrics where the metric key doesn't end with count, and (2) gauge metrics where the metric key does end with count. (APM-321104)

Update 96 (Build 1.224.96)

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

Cluster

  • Vulnerability: Enhanced access control in token creation. (APM-330727)
  • Fixed issue with access permission to Kubernetes entity page for some users with management zone permissions only. (APM-322118)
  • Users in a management zone no longer get a 403 HTTP error when opening Kubernetes pages. (APM-324758)
  • Fixed an issue in which, in certain circumstances, the number of ingestible events was reduced. (APM-322923)
  • Disabled Chromium auto-update. (APM-328535)

Update 99 (Build 1.224.99)

This cumulative update contains 1 vulnerability resolution and all previously released updates for the 1.224 release.

Cluster

  • Vulnerability: Enhanced access control in token creation. (APM-330727)

Update 102 (Build 1.224.102)

This cumulative update contains 3 vulnerability resolutions and all previously released updates for the 1.224 release.

Cluster

  • Vulnerability: In response to CVE-2021-44228 and CVE-2021-45046, applied the recommended mitigation measures of removing `org/apache/logging/log4j/core/lookup/JndiLookup.class` from the Log4j library. (APM-342160)
  • Vulnerability: In response to CVE-2021-44832, CVE-2021-45105, CVE-2021-44228 and CVE-2021-45046, applied the recommended mitigation measures of updating the log4j library to the latest version 2.17.1. In Premium HA installations log4j update will take place in near future. (APM-345946)
  • Vulnerability: In response to CVE-2021-44228 (Log4j vulnerability), JVM parameters have been extended for Dynatrace Server and Elasticsearch. (APM-341605)

Update 103 (Build 1.224.103)

This cumulative update contains 1 vulnerability resolution and all previously released updates for the 1.224 release.

Cluster

  • Vulnerability: In response to CVE-2021-44832, CVE-2021-45105, CVE-2021-44228 and CVE-2021-45046, applied the recommended mitigation measures of updating the log4j library to the latest version 2.17.1. In Premium HA installations log4j update will take place in near future. (APM-345946)