Dynatrace Managed release notes version 1.266

Published date: 2023-05-16

These release notes relate to Dynatrace Managed specific changes. To learn about general Dynatrace changes included in this Dynatrace Managed release, see:

• Dynatrace SaaS release notes version 1.266 and Dynatrace SaaS release notes version 1.265
• Dynatrace API changelog version 1.266 and Dynatrace API changelog version 1.265
• Dynatrace OneAgent release notes version 1.265

New features and enhancements

Operating systems support

• Added support for Amazon Linux 2023 all versions

Future Dynatrace Managed operating systems support changes

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

• Linux: SUSE Enterprise Linux 15.0
  • x86-64
  • Vendor announcement

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

• Linux: SUSE Enterprise Linux 12.4
  • x86-64
  • Vendor announcement

Past Dynatrace Managed operating systems support changes

The following operating systems are no longer supported since 01 October 2022

• Linux: SUSE Enterprise Linux 11.4
  • x86-64
  • Vendor announcement

The following operating systems are no longer supported since 01 January 2023

• Linux: Debian 9
  • x86-64
  • Vendor announcement
  • Last compatible version: 1.254
• Linux: SUSE Enterprise Linux 12.3
  • x86-64
  • Vendor announcement
  • Last compatible version: 1.254

The following operating systems are no longer supported since 01 March 2023

• Linux: Red Hat Enterprise Linux 8.2
  • x86-64
  • Vendor announcement
  • Last compatible version: 1.252
• Linux: Oracle Linux 8.2
  • x86-64
  • Last compatible version: 1.252

Resolved issues

• General Availability (Build 1.266.117)
• Update 122 (Build 1.266.122)

General Availability (Build 1.266.117)

The 1.266 GA release contains 46 resolved issues (including 1 vulnerability resolution).

Application Security

• Fixed an issue where the user can't select "View all" on vulnerable databases view. (RSA-9574)
• Added a banner to inform about changes to .NET framework runtime vulnerabilities. (RSA-9328)
• The comment to the vulnerability status change (muting/unmuting) is now limited to 250 characters. The change applies to the UI and the API. (RSA-9284)
• Pinning the "Hosts" page to a dashboard with an Application Security host coverage filter set no longer results in an error. (RSA-9545)

Autonomous Cloud

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

Cluster

• Vulnerability: Resolved an issue in the configuration API in Extension Framework 1.0. (TI-6681)
• Fixed the problem where the distributed error tab on the first span with errors shows 2 errors, but events only have one. (TI-6064)
• Fixed inconsistencies in checking IAM permission between MDA and Calculated Service Metrics. (TI-5961)
• Dynatrace technology is now visible for processes on the new host page. (HOST-2448)
• Leading and trailing ideographic space characters no longer break an LQL query. (Before the fix, ideographic space characters at the beginning or end of an LQL query would break the Log Monitoring Classic Log viewer when querying for logs. Now, ideographic space characters are treated like regular space characters.). (LOG-3243)
• Fixed the problem where some users could see the OneAgent health tab but can't select it. (TI-6273)
• Filtering on Deployment Status for OneAgent was not working in some particular cases (order of applying filters) when filtering by name was used and the filter contained ":" character. (DMX-3390)
• Fixed an issue changing from a graph chart to a single value, the execute endpoint was triggered three times. (EXA-5559)
• Metric event entity tag filter logic has been modified to consider a non-existing tag value as an `all` wildcard. This means that if no tag value exists, all possible values of the specified tag match, including a null value. Example: Suppose four hosts have tag values `Monitoring:True`, `Monitoring:False`, `Monitoring`, and no tag. A metric event tag filter "TAG equals Monitoring" would now match not only `Monitoring` (as before), but also `Monitoring:True` and `Monitoring:False`. (DAVIS-3965)
• Resolved inconsistencies in "Data explorer" tooltips for "Filter by" settings. (EXA-5226)
• Fixed an issue where alerting profile title filters were not applied for some built-in event types. (DAVIS-4412)
• Fixed an issue in which some metrics couldn't be queries during a metric correlation in the user interface. (DAVIS-4226)
• Due to wrongly calculated values, we temporarily disabled the Settings 2.0 feature for Key Performance Metrics (Apdex). (RUM-10654)
• Automatic configuration migration for Anomaly Detection (Host) no longer overwrites Alerting/Dealerting event thresholds settings with default values. But if migration was performed the custom settings are replaced by defaults. (HOST-2603)
• Fixed an issue in which a problem chart could stay in an error state even when the error was resolved. (DAVIS-4212)
• Fixed a case where very large problems could cause the entire problem manager to get stuck. (DAVIS-4587)
• RabbitMQ is now visible as main technology if mixed with technologies. (HOST-2460)
• Advanced queries with functions in summarize blocks are now correctly parsed by the query visitor. (LOG-3189)
• Fixed an issue where user can't proceed in the wizard at Remote Configuration Management. (DMX-3536)
• Resolved issue with failure to delete duplicate problems for premium HA, sometimes resulting in stuck open problems. (DAVIS-4345)
• The waterfall analysis no longer shows resources loaded by XHRs in frames twice. (RUM-9983)
• Problem notifications with a `{ProblemDetailsHTML}` or `{ProblemDetailsText}` placeholder now correctly contain a root cause section if only a single entity was affected. (DAVIS-4408)
• Log content spaces are no longer trimmed in the "Logs" table. (LOG-3054)
• Corrected calculated data points displayed when creating a custom metric. (LIMA-7071)
• Corrected information on metric calculation for custom metrics. (LIMA-7072)
• Fixed an issue that caused the crashing of entity details pages. (TI-6517)
• Resolved exception occurring when saving logs to CSV. (LOG-3148)
• Fixed an issue with missing Availability charts on host details pages for hosts with OneAgent 1.263 and earlier. (HOST-2465)
• For remote configuration management, in the message stating that "You cannot perform the remote configuration action on all of [entities] that you have selected," the link for downloading a list of the inapplicable entities now correctly downloads the list. (DMX-3544)
• Automatic configuration migration for Anomaly Detection (Host) no longer overwrites Alerting/Dealerting event thresholds settings with default values. (HOST-2691)
• All matchers within the log pipeline (events, metrics, log processing) in DQL syntax can now use case-sensitive attributes. This means that, when using DQL, you need to make sure that the case of the characters in attributes used in the criteria for matchers corresponds to the case of the characters in the attributes in the log record. (LOG-3290)
• Fixed an issue where hybrid sessions with only errors were dropped. (RUM-10105)
• An attempt to delete an attribute that either did not exist or has been deleted now returns a proper validation message explaining that the attribute cannot be found. (TI-6076)
• Due to a bug, we have currently disabled the ability to duplicate an existing configuration in metric events. The fix is already underway and will be available shortly. (DAVIS-4437)

Session Replay

• Users with proper permissions can access the Session Replay Enablement and Cost control page. (SR-2175)

Synthetic monitoring

• Fixed a problem with failure to store information about a customized script when an execution failed to be triggered for some reason. (SYNTH-4588)
• Improved the "Synthetic monitor health" dashboard tile for environments with many open problems. (Resolves issue with the tile not displaying an unhealthy monitor as red.). (SYNTH-4722)
• Update of a synthetic monitor no longer triggers an on-update execution. (Resolves issue with unexpected execution of deactivated monitors.). (SYNTH-4770)
• Fixed an issue related to the Synthetic browser monitor configuration migration, which could lead some environments to fail to start after the upgrade. (SYNTH-4745)

managed

• Fixed and issue where the self-monitoring OneAgent hasn't been downloaded during installation and upgrade. (CLD-6658)

rest api

• Fixed an issue in which the fold operator with aggregation could disable the default operator in metric selectors. (CLUSTER-5348)

Update 122 (Build 1.266.122)

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

Cluster

• Metric events metric key based configurations hard limit increased to support metric events Settings 2.0 migration for customers with customized ConfigV1 limit. (DAVIS-4713)

managed

• Fixed and issue where the self-monitoring OneAgent hasn't been downloaded during installation and upgrade. (CLD-6658)