Dynatrace Managed release notes version 1.226

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 update system user used on Dynatrace Managed node via "reconfigure.sh" script.

ServiceNow integration change

If you have integrated ServiceNow and Dynatrace, please refer to our Send Dynatrace notifications to ServiceNow documentation for important updated instructions on integrating Dynatrace with ServiceNow. Dynatrace support for the Dynatrace Service Graph Connector app ends on December 31, 2021. In its place, we recommend that you configure the dedicated Service Graph Connector for Observability application from ServiceNow.

Operating systems support

    Current Dynatrace Managed operating systems support changes

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

    Past Dynatrace Managed operating systems support changes

    The following operating systems are no longer supported since 01 July 2024
    The following operating systems are no longer supported since 01 August 2024

    Resolved issues

    General Availability (Build 1.226.102)

    The 1.226 GA release contains 45 resolved issues.

    Cluster

    • Fixed switch for enabling/disabling rules on "OS service monitoring" page. (APM-321606)
    • Improved performance of Log Monitoring aggregation queries. (APM-320500)
    • On "Deployment status" > "ActiveGates" page, renamed ActiveGate module from `DB Insight` to `Database insights`. (APM-319086)
    • Custom and undefined attribute keys are no longer case sensitive. (APM-320182)
    • Fixed issue that made it impossible to switch Extension Execution Controller on or off. (APM-323227)
    • Switch "Monitor the environment for hosts in infrastructure-only monitoring mode" in plugin settings now works correctly for JMX plugins. (APM-320690)
    • On "Deployment status" > "ActiveGates" page, renamed ActiveGate module from `z/OS` to `zRemote`. (APM-320074)
    • 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)
    • Data explorer now uses the correct name dimension keys for the :names operator in metric selectors when custom generic entity types are used. (APM-309971)
    • Fixed a bug in which the GA version of Kubernetes events was not properly enabled when selecting "Activate Kubernetes events analytics for all clusters" or "Enable Kubernetes events visibility". (APM-321622)
    • Resolved infrequent issue in which an event that is configured to not merge (e.g., CUSTOM_ALERT event type when used with the custom events for alerting) would still merge with another event. (APM-320550)
    • When migrating a custom chart with two tag filters applied to the `Data explorer`, the tags are now correctly applied with an AND combination instead of an OR. The migrated chart is opened in Code mode in the `Data explorer`, not the standard Build mode, as the Build mode does not support AND filter values. (APM-318454)
    • Fixed filtering of management zones of remote environments. (APM-320812)
    • Fixed an issue in which, in certain circumstances, the number of ingestible events was reduced. (APM-322923)
    • Fixed issue with access permission to Kubernetes entity page for some users with management zone permissions only. (APM-322118)
    • Resolved issue that led to failed query execution when adding tile from dashboard and then adding metric in `Data explorer`. (APM-321248)
    • Added `Location` link to header of user details page. (APM-316552)
    • Improved detection of page and page group for RUM actions. (APM-318346)
    • Fixed an issue where calculated service metrics would randomly lose data. (APM-316585)
    • Fixed an issue in which a single value query (i.e., "resolution=Inf") would incorrectly return a result of `0` for a counter metric. (APM-318188)
    • Dashboard API calls changing the preset state of a user-built dashboard now correctly function. (APM-322917)
    • Resolved issue in which some filters were not removed when selecting the remove filter button for location, browser, or OS. (APM-319726)
    • Resolved issue with attaching images to live chat. (APM-321268)
    • Dashboards filtered by `Deployment type` now correctly apply the filter. (APM-317158)
    • Improved infographic display to prevent extended user information from being accidentally overwritten. (APM-315402)
    • 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)
    • Resolved issue with display of detailed JVM memory metrics on details page for process group instance. (APM-322146)
    • Fixed issue in which adding whitespace to the end of a deep object access input in the "Request attributes" page would crash the web UI. (APM-320305)
    • When using the `/api/config/v1/extensions` and `/api/config/v1/plugins` endpoints to post a configuration for a remote plugin, you now need to provide the ID of an ActiveGate extension module that is online on the tenant. Use `https://{your-environment-id}.live.dynatrace.com/api/config/v1/extensions/activeGateExtensionModules` to get the IDs of all ActiveGate extension modules. Configuration for a non-existent remote plugin is rejected. (APM-310674)
    • Fixed issue in which, when the geolocation of a private location was reconfigured in the settings, the private location was subsequently not taken into account for anomaly detection for browser monitors. (APM-321860)
    • Improved maintenance window evaluation performance when a significant number of management zones are configured. (APM-321489)
    • The Save button is now enabled when an alias is added to a metric. (APM-321302)
    • Top list chart tile's sort order now properly reflects the endpoint results. (APM-323845)
    • Filters based on Kubernetes name now implement a "contains" behavior (instead of a "startsWith" behavior) to be consistent over all Kubernetes monitoring pages. (APM-317696)
    • 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)
    • 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)
    • Fixed an issue in which it was not possible to update an extension due to a non-present metric used in a metric expression. (APM-317750)
    • When exporting a dashboard with a tile reading data from a remote environment and a management zone from that environment set as a filter, the management zone is now correctly included in the dashboard JSON. (APM-319652)
    • Filter for session properties (double, date, string...) was not working properly when coming from GWT page to Angular page. Now all filters for session properties are correctly mapped. (APM-319773)
    • Fixed a bug in the Kubernetes pod details, where too many processes were shown. (APM-321838)
    • Data explorer: `Visual settings` and `Axes` labels now display metric ID (instead of nothing) when metric name is null. (APM-320521)
    • Filtering by timestamp field in log viewer v2 no longer causes error. (APM-309687)
    • Fixed issue that caused inconsistent JSON responses when aggregating on an empty set of problems. (APM-317294)
    • IDs of environments created via PUT ​'/api/cluster/v2/environments​/{id}' are now restricted to a set of characters ([a-zA-Z0-9_-]{1,70}). Use of some other characters previously caused environments to be unable to start. (APM-317514)
    • Request attributes related to web requests are now correctly set when taken from the client-side attachment and put on the server-side service call. (APM-317742)

    Update 103 (Build 1.226.103)

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

    Cluster

    • Resolved issue that is caused an error when navigating to the Data explorer form some tiles that were created before version 226. (APM-326026)

    Update 104 (Build 1.226.104)

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

    Cluster Management Console

    • During the fresh installation we had 5 minutes timeout for starting of Dynatrace server process. To fix the problem with long starting server, the timeout was increased to 10 min. (APM-332849)

    Update 116 (Build 1.226.116)

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

    Cluster

    • Resolved an issue that could cause rollbacks to old settings. (APM-327754)
    • Fixed an issue with Davis not correctly following up on baseline trigger events, sometimes not finding an explanation. (APM-325532)
    • Key requests with a colon (":") in name can now be removed. (APM-327327)

    Update 126 (Build 1.226.126)

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

    Cluster

    • Vulnerability: Enhanced access control in token creation. (APM-330727)
    • Fixed an issue with Davis not correctly following up on baseline trigger events, sometimes not finding an explanation. (APM-325532)
    • Disabled Chromium auto-update. (APM-328535)

    Update 128 (Build 1.226.128)

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

    Cluster

    • Fixed not working SNMP host screen when there was missing metric data. (APM-328743)

    Update 132 (Build 1.226.132)

    This cumulative update contains 2 vulnerability resolutions and all previously released updates for the 1.226 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-44228 (Log4j vulnerability), JVM parameters have been extended for Dynatrace Server and Elasticsearch. (APM-341605)

    Update 133 (Build 1.226.133)

    This cumulative update contains 2 resolved issue (including 1 vulnerability resolution) and all previously released updates for the 1.226 release.

    ComponentResolved issues
    Cluster1 (1 vulnerability)
    Cluster Management Console1

    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)

    Cluster Management Console

    • Upgrade log4j to v2.17.1 for Premium High Availability. (APM-346554)