Dynatrace Managed release notes version 1.230

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

  • Reduce Elasticsearch backup snapshots retention to 5 days. Old snapshots will be automatically removed after the upgrade.

  • Managed hardware requirements have been updated for required IOPS per cluster node to reflect current needs to provide on-demand analysis.

  • Problems API v2 now includes event evidence data as part of the event details.

  • With this release, svchost.exe is excluded from injection. This eliminates certain timeout issues with Windows Server 2019 at boot.

  • You can now clone a service-level objective (SLO) by selecting More () > Clone SLO in the Actions column of the Service-level objectives page. This opens the Add new SLO page already filled in with the settings from the cloned SLO.

  • Service-level objectives are now management zone–aware. The Service-level objectives page is filtered by management zones selected in the global filter for management zones. You can see only the SLOs that belong to the management zones you have access to, or to SLOs that belong to no management zone. An SLO belongs to a management zone by adding the management zone name or ID in the Entity selector. This also affects the Service-level objectives tile in the dashboard where you can only see data for the Service-level objectives that belong to management zones you have access to. Otherwise, an "Access denied" message will be shown on the tile instead.

  • Custom events for alerting using the Build tab and advanced query mode now apply the same metric dimension limits that are applied to Code-tab-based configurations.

  • Outage-handling settings of browser monitors and HTTP monitors can now be managed via the Settings API. As a result, it's now possible to set default for outage-handling settings at the environment level for all browser monitors or all HTTP monitors. You can override these at the monitor level.

  • Real user traffic has been added to the world map on the browser monitor details page.

  • Prometheus metrics from exporters in Kubernetes that aren’t running on a OneAgent-monitored node now consume DDUs.

  • Events API v2 has been updated.

  • The Kubernetes monitoring pages for workloads and pods are extended with a new log card that shows the Kubernetes logs. Note that Log monitoring must be enabled.

  • Charting of timeslots in service data–related pages like multidimensional analysis has been unified with Data explorer.

Local self-monitoring metrics

A newly created environment for purely self-monitoring purposes is created on the cluster. It aggregates self-monitoring metrics from all environments in the cluster. The self-monitoring environment is named Local-Self-Monitoring. It is excluded from all usage consumption and does not contribute to the monitoring consumption. You cannot connect any OneAgents, ActiveGates, Extensions nor set up Synthetic monitoring in the environment. See, Local self-monitoring environment. More details will come in a separate blog post, shortly.

Metrics API: dimension keys

The Metrics API v2 no longer supports legacy dimension keys in metric selectors. Use dt.entity.<entity_type>, not <entity_type>. For example, for a host dimension, use dt.entity.host, not Host. For more information, see Metric ingestion protocol.

Operating systems support

Future Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 February 2022

  • Linux: CentOS 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 8.0
  • Linux: Debian 8
  • Linux: Red Hat Enterprise Linux 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 8.0
  • Linux: Oracle Linux 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 8.0
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.226

The following operating systems will no longer be supported starting 01 March 2022

  • Linux: CentOS 8.3
  • Linux: Red Hat Enterprise Linux 8.3
  • Linux: Oracle Linux 8.3
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.228

The following operating systems will no longer be supported starting 01 May 2022

  • Linux: CentOS 7.6, 8.1
  • Linux: Red Hat Enterprise Linux 7.6, 8.1
  • Linux: Oracle Linux 7.6, 8.1
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.232

The following operating systems will no longer be supported starting 01 June 2022

  • Linux: Ubuntu 20.10

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

  • Linux: Red Hat Enterprise Linux 7.8
  • Linux: Oracle Linux 7.8
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.246

The following operating systems will no longer be supported starting 01 August 2022

  • Linux: CentOS 7.7
  • Linux: CentOS 7.8
  • Linux: Red Hat Enterprise Linux 7.7
  • Linux: Oracle Linux 7.7
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.238

The following operating systems will no longer be supported starting 01 October 2022

The following operating systems will no longer be supported starting 01 November 2022

  • Linux: Ubuntu 21.04

The following operating systems will no longer be supported starting 01 January 2023

The following operating systems will no longer be supported starting 01 March 2023

  • Linux: CentOS 8.2
  • Linux: Red Hat Enterprise Linux 8.2
  • Linux: Oracle Linux 8.2
    • x86 (64bit-only)
    • Last compatible Dynatrace Managed version: 1.252

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

The following operating systems will no longer be supported starting 01 January 2024

The following operating systems will no longer be supported starting 01 August 2024

The following operating systems will no longer be supported starting 01 November 2024

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

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

The following operating systems will no longer be supported starting 01 May 2028

The following operating systems will no longer be supported starting 01 November 2028

The following operating systems will no longer be supported starting 01 November 2030

Resolved issues

Cluster Managed (Build 1.230.100)

45 total resolved issues (1 vulnerability)

Component Resolved issues
ActiveGate 1
Cluster 40 (1 vulnerability)
Cluster Management Console 2
Infrastructure monitoring solution 1
User Interface 1

ActiveGate

  • Corrected the unit for the `Response time avg` metric for Azure App Services. (APM-323489)

Cluster

  • Improved handling of whitespace characters on "Log events" page. (APM-323182)
  • Resolved issue in which DDUs: Metrics pool: Consumption was sometimes too low, including byEntity and total metrics, which then could unexpectedly differ from byMetric and byEntity. (APM-329863)
  • You are now able to access the database or service detection anomaly detection settings UI when access to these settings is managed via IAM policies. (APM-332961)
  • Fixed an issue in which baseline events sometimes led to an incomplete root cause analysis. (APM-335305)
  • Settings writer policy extended with Settings read. (APM-333008)
  • Kubernetes event reason strings are now truncated when they exceed valid length. (APM-326520)
  • Management zone rule definition for "Rule applies to": "Queue" no longer results in web UI crash. (APM-326121)
  • Improved the performance of loading the pod information on the Kubernetes workloads details and namespace details pages. (APM-330022)
  • Log Viewer: whitespace characters are now trimmed from the table column filter select box. After copying values, columns are displayed properly and facets are turned off. (APM-319051)
  • Resolved client-side exception caused by error on "User sessions" page. (APM-325735)
  • A maintenance window set to occur during a daylight saving time change is no longer invalid. (APM-326998)
  • Calculated service metrics: use of bracket characters in the metric key property field no longer breaks validation instead of returning a constraint violation message. (APM-329616)
  • Resolved error that sometimes when resulted selecting the Problems tile. (APM-330518)
  • Improved consistency of "Session details" page display of application type. (APM-324830)
  • Improved accuracy of user count displayed on application "Error details" page. (APM-328317)
  • Improved layout of Davis Security Advisor advice. (CASP-11809)
  • When filtering "User sessions" page for user tags with double quotes, filter suggestions are now correctly displayed. (APM-325680)
  • Displayed data retention period is now correct for trial tenants. (APM-327900)
  • Improved drilldowns from custom alerts to mobile apps. (APM-328887)
  • The `entitySelector` predicate `softwareTechnologies` now also supports custom technologies sent, for example, via custom devices. (APM-329754)
  • Fixed an issue in which, for custom "User sessions" metrics and custom "Log Monitoring v2" metrics on multi-data center Dynatrace Managed clusters, some dimension tuples sometimes disappeared, depending on the query timeframe. (APM-327203)
  • The breadcrumbs in the header bar are now consistent over all Kubernetes monitoring pages. (APM-330552)
  • Filter suggestions for a Kubernetes cluster in custom charting no longer show "UNKNOWN " instead of the proper cluster name. (APM-331799)
  • Fixed timing issue that could result in a 403 instead of properly redirecting to the "Application Security Overview" page. (CASP-11413)
  • Starting new diagnostics is possible only for running ActiveGates. For offline ActiveGates, only viewing diagnostics history is allowed. (APM-328504)
  • Now able to filter for `missing` request attributes in multidimensional analysis and trace list. (APM-333359)
  • Improved formatting of mobile stack traces. (APM-330777)
  • Kubernetes clusters without a settings configuration are no longer excluded from the cluster list. (APM-331591)
  • Vulnerability: Improved validation of RUM web application custom config properties. (APM-329664)
  • Improved "Data explorer" behavior when resizing the window on Firefox and Safari. (APM-329108)
  • The monitor-level performance threshold is now correctly duplicated when the "Duplicate" feature of the Synthetic monitors list is used. (APM-326798)
  • Events open for more than 60 days are automatically closed correctly. (APM-329505)
  • It's no longer possible to create stored metric queries for metrics without the required "func:" prefix through the settings endpoint or extensions. (APM-328522)
  • Improved navigation timings for complex actions that contain multiple timings. (APM-329359)
  • Data explorer: improved display of warning messages. (APM-328451)
  • Improved handling of chart X axis naming to retain new name when query is rerun or timeframe is changed. (APM-329198)
  • Resolved an inconsistency in the API event selector documentation. (APM-330280)
  • Resolved issue with display of the username, password, and token fields in web UI of local activation. (APM-329218)
  • A warning is displayed if a user without sufficient permission tries to edit remote environment settings. (APM-329547)
  • Fixed a bug related to third party resources in application analysis. (APM-334399)

Cluster Management Console

  • Triggering node removal using the API explorer no longer produces an error. (APM-331939)
  • User sessions with Session Replay for mobile are now correctly calculated as part of the total number of sessions displayed on the environment details page. Previously, the displayed total number was slightly greater than actual consumption. (APM-331868)

Infrastructure monitoring solution

  • Dynatrace Hub, extension details page: permission checks are now correct in activation flow. (APM-325613)

User Interface

  • The "Recent" tab of the global timeframe selector now shows correct selection of recent timeframe settings. (APM-329724)