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

    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.230.100)

    The 1.230 GA release contains 49 resolved issues (including 1 vulnerability resolution).

    ComponentResolved issues
    Cluster46 (1 vulnerability)
    Cluster Management Console2
    Infrastructure monitoring solution1

    Cluster

    • Vulnerability: Improved validation of RUM web application custom config properties. (APM-329664)
    • Improved handling of whitespace characters on "Log events" page. (APM-323182)
    • Management zone rule definition for "Rule applies to": "Queue" no longer results in web UI crash. (APM-326121)
    • Settings writer policy extended with Settings read. (APM-333008)
    • Fixed an issue in which baseline events sometimes led to an incomplete root cause analysis. (APM-335305)
    • Restored support for Debian 9 and 10. (APM-336358)
    • 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)
    • 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)
    • Kubernetes event reason strings are now truncated when they exceed valid length. (APM-326520)
    • Improved user action classification (some user actions of action type "Load" were classified as action type "Xhr"). (APM-333176)
    • Improved layout of Davis Security Advisor advice. (CASP-11809)
    • The `entitySelector` predicate `softwareTechnologies` now also supports custom technologies sent, for example, via custom devices. (APM-329754)
    • Improved accuracy of user count displayed on application "Error details" page. (APM-328317)
    • Resolved client-side exception caused by error on "User sessions" page. (APM-325735)
    • Improved the performance of loading the pod information on the Kubernetes workloads details and namespace details pages. (APM-330022)
    • Improved drilldowns from custom alerts to mobile apps. (APM-328887)
    • Log Monitoring v2 histogram queries are now executed significantly faster. (APM-332250)
    • Resolved error that sometimes when resulted selecting the Problems tile. (APM-330518)
    • Users are now able to view process group naming settings if they have config read permission. (APM-333614)
    • 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)
    • 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)
    • The "Recent" tab of the global timeframe selector now shows correct selection of recent timeframe settings. (APM-329724)
    • When filtering "User sessions" page for user tags with double quotes, filter suggestions are now correctly displayed. (APM-325680)
    • 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)
    • Displayed data retention period is now correct for trial tenants. (APM-327900)
    • Improved consistency of "Session details" page display of application type. (APM-324830)
    • Starting new diagnostics is possible only for running ActiveGates. For offline ActiveGates, only viewing diagnostics history is allowed. (APM-328504)
    • 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 <CLUSTER_ID>" instead of the proper cluster name. (APM-331799)
    • The monitor-level performance threshold is now correctly duplicated when the "Duplicate" feature of the Synthetic monitors list is used. (APM-326798)
    • Fixed timing issue that could result in a 403 instead of properly redirecting to the "Application Security Overview" page. (CASP-11413)
    • Improved "Data explorer" behavior when resizing the window on Firefox and Safari. (APM-329108)
    • Improved formatting of mobile stack traces. (APM-330777)
    • Corrected the unit for the `Response time avg` metric for Azure App Services. (APM-323489)
    • Now able to filter for `missing` request attributes in multidimensional analysis and trace list. (APM-333359)
    • Kubernetes clusters without a settings configuration are no longer excluded from the cluster list. (APM-331591)
    • Improved navigation timings for complex actions that contain multiple timings. (APM-329359)
    • Improved handling of chart X axis naming to retain new name when query is rerun or timeframe is changed. (APM-329198)
    • Fixed a bug related to third party resources in application analysis. (APM-334399)
    • 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)
    • Resolved issue with display of the username, password, and token fields in web UI of local activation. (APM-329218)
    • Resolved an inconsistency in the API event selector documentation. (APM-330280)
    • A warning is displayed if a user without sufficient permission tries to edit remote environment settings. (APM-329547)
    • Events open for more than 60 days are automatically closed correctly. (APM-329505)
    • Data explorer: improved display of warning messages. (APM-328451)

    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)

    Update 127 (Build 1.230.127)

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

    ComponentResolved issues
    Cluster17 (1 vulnerability)
    Cluster Management Console3

    Cluster

    • Vulnerability: In response to CVE-2021-44228 (Log4j vulnerability), JVM parameters have been extended for Dynatrace Server and Elasticsearch. (APM-341605)
    • Filter suggestions have been corrected for "User sessions" and user details pages. (APM-332005)
    • False-positive monitoring alerts caused by internal communication timeouts have been eliminated. (APM-337001)
    • "Server overloaded" popup message no longer displayed on larger deployments. (APM-339014)
    • Process group monitoring overrides now work correctly for new settings. (APM-337269)
    • Resolved issue causing server error during fetch of dashboard tile data. (APM-331846)
    • Resolved issue causing high CPU load on cluster and partly missing host unit calculation. (APM-337680)
    • Kubernetes workload and pod details pages no longer crash when user doesn't have `View logs` permission. (APM-337632)
    • Corrected issue with tile threshold configuration in dashboards created using API. (APM-338146)
    • Removed the "Show all process groups" button in the "Affected Process Groups" pane of the "Security overview" page. (CASP-12511)
    • Toggling "Show legend" no longer breaks dashboard tile. (APM-336560)
    • Resolved issue that made problem details page inaccessible for affected problems. (APM-338039)
    • Toggling "Show legend" for a table tile no longer removes thresholds. (APM-333052)
    • Resolved issue with enabling/disabling container monitoring for BPM, Containerd, CRI-O, and Winc. (APM-337609)
    • Corrected an issue with process group monitoring overrides. (APM-339558)
    • Fixed an issue that caused reading of invalid container monitoring configuration in some cases. (APM-339100)
    • Resolved issue in "Data explorer" in which splitBy information was dropped when a filter condition was added to a query. (APM-332819)

    Cluster Management Console

    • Data ingested via Log Monitoring v2 is no longer included by default in backup to avoid overconsumption of resources. (APM-336489)
    • Resolved issue in which, when using REST API to modify permissions for a given group to selected environments and management zones, all of that group's other permissions were cleared for all environments and management zones. (APM-338188)
    • Resolved issue in which, if there was no configuration of permissions to management zones for a given user group, it was impossible to create this configuration via public REST API. (APM-339033)

    Update 138 (Build 1.230.138)

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

    ComponentResolved issues
    Cluster3 (1 vulnerability)
    Cluster Management Console1

    Cluster

    • Vulnerability: In response to CVE-2021-44228 (Log4j vulnerability), JVM parameters have been extended for Dynatrace Server and Elasticsearch. (APM-341605)
    • Improved baselining alert sensitivity for Settings 2.0 configurations to ensure appropriate alerting. (APM-341879)
    • Restored support for CentOS Stream 8. (APM-341686)

    Cluster Management Console

    • Corrected proxy certificate import issue. (APM-341894)

    Update 139 (Build 1.230.139)

    This cumulative update contains 2 resolved issue (including 1 vulnerability resolution) and all previously released updates for the 1.230 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)
    • Resolved issue with cluster memory saturation and constant suspension/GC. (APM-342772)

    Update 148 (Build 1.230.148)

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

    Cluster

    • Vulnerability: Updated Log4j in Elasticsearch client to version 2.17.1. (APM-345471)

    Update 151 (Build 1.230.151)

    This cumulative update contains 2 resolved issue (including 1 vulnerability resolution) and all previously released updates for the 1.230 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)