Dynatrace Managed release notes version 1.258

Rollout start: Jan 30, 2023

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

Mission Control connection status

You can now check details of the Mission Control connection status from the Cluster Management Console. In case of an issue with authentication to Mission Control, you can reset credentials and re-establish a successful connection. This operation might be required when you are restoring the cluster from backup or you've experienced a "split brain" situation of your cluster. To access the new Mission Control connection status page, go to Licensing and select Check Mission Control connection.

mission control connection status page

Procedure to Premium HA - Replicate nodes across DCs was updated

We've automated and improved the procedure to replicate cluster nodes across DCs to make it easier and more resilient. If you're planning to implement a Premium High Availability deployment, please note the changes.

New cluster event in case of a cluster node's inability to receive OneAgent traffic

To better help you in the event of an unsuccessful and incomplete start of all Dynatrace Managed services on a cluster node, we've added additional alerting mechanisms. If you're alerted, please try to carry out the suggested action before reaching out to support. This should generally reduce problem resolution time. At first, when a cluster node can't receive OneAgent traffic, the affected node is highlighted with a red tile on the cluster deployment overview page and in the corresponding row in the cluster node deployment page. Additionally, a cluster event message is generated with the following content: Summary: "A cluster node can't receive OneAgent traffic" Description: "The cluster node id can’t receive OneAgent traffic. Try to restart the cluster node. If this doesn’t fix the problem, generate the support archive and provide it to the Support team."

Upgraded technical components

To take advantage of performance improvements, the latest security-vulnerability enhancements, and latest bug fixes, we've upgraded JRE for the following cluster node components:

  • Cassandra now uses JRE 8u352
  • Other components now use JRE 11.0.17 Additionally, we've upgraded Cassandra to version 3.11.14.

Extended Operation Systems support end-of-life with version 1.260

Six months ago, we extended the support policy for selected operating system releases. Under these exceptions, you could still upgrade to newer versions of Dynatrace Managed on these OS releases, but you could no longer install any new cluster nodes on them. Now, we remind you that Managed version 1.258 will be the last version that you can run on:

  • Red Hat Enterprise Linux 7.0 - 7.8
  • Red Hat Enterprise Linux 8.0 - 8.3
  • CentOS 7.0 - 7.8
  • CentOS 8.0 - 8.4
  • Oracle Linux Server 7.0 - 7.8
  • Oracle Linux Server 8.0 - 8.3
  • SUSE Enterprise Linux 12.1 - 12.3
  • Ubuntu 21.04

Operating systems support

    Current Dynatrace Managed operating systems support changes

    The following operating systems will no longer be supported starting 01 November 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
    The following operating systems are no longer supported since 01 October 2024

    Resolved issues

    General Availability (Build 1.258.110)

    The 1.258 GA release contains 28 resolved issues.

    Component
    Resolved issues
    1
    1
    25
    1

    Application Security

    • Fixed the link text in the UI to match the linked documentation. (RSA-7575)

    Autonomous Cloud

    • The deployment page now references the newly released Dynatrace Operator v0.10.1. (K8S-4385)

    Cluster

    • Fixed extracting generic entities from event metadata that was unintentionally disabled for Dynatrace Managed deployments. The feature is now available. (DAVIS-3137)
    • Previously, when querying the Problems API v2 using a problem selector with 'severityLevel(INFO)', a 500 internal server error occurred. Now a 400 error is correctly returned with a proper error message. (A problem, by definition, never has severity level INFO.). (DAVIS-2809)
    • Added configurable limit for the number of top dimensions in multidimensional analysis view. (TI-4678)
    • The tag placeholder for problem notifications now supports contextual tags. (DAVIS-3003)
    • Customization of the OneAgent installer on the deployment screens for Windows, Linux & AIX by configuring network zone modifies the download URL, so the customization step was moved to be before the download step. Additionally, for clarity, the network zone parameter is also provided in the installation command, however, it is not required for the already downloaded and customized installers. (DMX-2624)
    • To prevent a timeout when creating a JMX/PMI extension (Settings > Monitoring > Monitored technologies > Add new technology monitoring > Add JMX/PMI extension > Use JMX/PMI extensions editor), the number of example processes used as a metrics source for the JMX extensions creator is now limited to 1000. (TI-4138)
    • Fixed an issue causing metric evidences to show an invalid start- and end-timestamp. (DAVIS-2965)
    • Fixed an issue that prevented a user with correct IAM permissions from creating a custom metric with regex condition. (TI-4287)
    • Fixed an issue in which the entity extraction and remapping (for generic topology) from event properties worked only via the v2 Event REST API. Now all event ingest channels (such as log events or metric events) are supported. (DAVIS-2922)
    • Fixed numeric request attribute service filter in multidimensional analysis and distributed traces. (TI-4544)
    • Fixed the changed aggregation of metric events using the metric `builtin:kubernetes.container.restarts`. (APM-391034)
    • Calculated service metrics API update operations can now be made even when the metrics limit has been reached. (Solves `Limit reached for service metrics`.). (TI-4214)
    • Fixed an issue with creating a management zone filter. When a user initially chose the zone name in the dropdown, the ID was shown instead of the zone name. (DAVIS-2816)
    • Fixed an issue with opening host or process group instance details page that might lead to 500 error blocking access to those pages for customers which were using legacy log monitoring v1 with combination of events extraction functionality. (APM-393678)
    • Fixed the validation error that was shown redundantly at start when creating an application detection rule. (RUM-8460)
    • Filter suggestions have been improved to avoid issues when fetching data. (Solves problem with inconsistent results from user session filters.). (RUM-8036)
    • Changed the message about no injection for the blocklisted process from "Activation of deep monitoring was unsuccessful" to "Cannot enable deep monitoring for this process". (HOST-1853)
    • Fixed metric schema pagination problem that was discarding metadata selector. (Solves Metrics API NextPageKey not working when applying metadataSelector.). (APM-391833)
    • Fixed a page crash appearing when a user lacking permission opens the Dynatrace environment page. (DAVIS-3036)
    • Fixed a problem that caused a queue name to unexpectedly change from trace to trace. (TI-4184)
    • On the "Response time analysis" page, the "View method hotspots" button is now available regardless of timings. (TI-4507)
    • Calculated service metric dimensions with more than 21,845 characters now will be truncated to that size instead of not booking the metric data point. (TI-4116)
    • Corrected link to documentation from the "Business event processing" page. (APM-392469)
    • Support for OAuth 2.0 in webhook problem notifications was recently added, but the new feature created an API breaking change by requiring a new property to be specified in POST requests to the Settings 2.0 API for the problem notifications schema. The property is now optional so as not to break API integrations with existing payloads. (DAVIS-3319)
    • Fixed an infrequent problem on the provider details page for mobile and custom applications. (RUM-8981)

    RUM

    • Fixed single value visualization of USQL. (APM-392812)

    Update 115 (Build 1.258.115)

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

    metric low-level

    • Fixed an issue when the Container Group instance metric queries can cause data loss by triggering ALR. (CLUSTER-4459)

    Update 123 (Build 1.258.123)

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

    Cluster

    • Fixed an issue in which metric events created or modified via Metric events API starting from version 1.257 had incorrect audit information. This bug neither impacts the authentication of API calls nor reveals secret parts of the API tokens to other Dynatrace users. (DAVIS-3420)

    Update 128 (Build 1.258.128)

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

    Autonomous Cloud

    • An issue with the "Kubernetes node not ready" alert was fixed, which could lead to the alert not triggering, even if the "node not ready" condition was fulfilled. (K8S-4942)

    Update 129 (Build 1.258.129)

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

    Cluster

    • Fixed: user with Management Zone only access rights might get unexpected 403 page when editing host's plugins configuration. (TI-5183)

    Update 133 (Build 1.258.133)

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

    Cluster

    • Fixed issue where RUM was not disabled on Dynatrace Managed environments when the DEM quota was exceeded. (LIMA-6257)
    • We fixed an issue for Managed Multi-DataCenter failover handling where the event/problem handling could get stuck. (DAVIS-3625)

    Update 134 (Build 1.258.134)

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

    Cluster

    • Fixed a problem where the RUM enablement setting on process group level was ignored, leading to unintentional enabling or disabling of RUM for certain process groups. (RUM-9579)

    Update 139 (Build 1.258.139)

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

    Synthetic monitoring

    • Fixed a problem occurring during the update of Managed cluster where the cluster didn't allow the "automatic cluster update" due to issues with the custom.properties file. (SYNTH-4150)

    Update 149 (Build 1.258.149)

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

    Cluster

    • Vulnerability: Resolved an issue in the configuration API in Extension Framework 1.0. (TI-6681)
    • Fixed and issue where metric event duplication breaks alerting for metric events created in earlier configuration version. (DAVIS-4508)