Dynatrace Managed release notes version 1.264
Published date: 2023-04-21
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
Upgrade from Dynatrace Managed to SaaS
Get on board with the latest Dynatrace innovations and start your upgrade journey with us now! Plan and execute your seamless upgrade to SaaS with our comprehensive step-by-step guide. In the guide sections, we provide you with the essentials for a successful upgrade from Dynatrace Managed to SaaS. To learn more read Upgrade from Managed to SaaS deployment.
OpenSSL library
The OpenSSL library, used by the Nginx service, was updated to version 1.1.1t
for increased resilience and security.
Updated Managed installer to use JRE 8u362 and JRE 11.0.18
To take advantage of performance improvements, the latest security-vulnerability enhancements, and bug fixes, we've upgraded JRE for Cassandra and will now use JRE 8u362. All other components will now use JRE 11.0.18.
New Log drop rules setting
Dynatrace Managed allows you to exclude specific log sources for storage. Using logs matched by rules, you can control which logs should not be stored in your deployment but still be processed by log metrics and log events.
Operating systems support
Future Dynatrace Managed operating systems support changes
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 July 2023
- Linux: SUSE Enterprise Linux 15.0
- x86-64
- Vendor announcement
The following operating systems are no longer supported since 01 November 2023
- Linux: SUSE Enterprise Linux 15.1, 15.2, 15.3
- x86-64
- Vendor announcement
- Last compatible version: 1.268
Resolved issues
- General Availability (Build 1.264.102)
- Update 109 (Build 1.264.109)
- Update 120 (Build 1.264.120)
- Update 127 (Build 1.264.127)
- Update 135 (Build 1.264.135)
- Update 141 (Build 1.264.141)
- Update 142 (Build 1.264.142)
- Update 143 (Build 1.264.143)
- Update 150 (Build 1.264.150)
- Update 155 (Build 1.264.155)
- Update 164 (Build 1.264.164)
General Availability (Build 1.264.102)
The 1.264 GA release contains 26 resolved issues.
Component | Resolved issues |
---|---|
Application Security | 4 |
Autonomous Cloud | 1 |
Cluster | 13 |
Synthetic monitoring | 1 |
User Interface | 1 |
auto update | 1 |
entity query | 1 |
managed | 1 |
metric query | 1 |
metric selector | 1 |
slo | 1 |
Application Security
- Fixed incorrectly displaying related workloads on the "Third-party vulnerabilities" details page in the rare cases where processes of different workloads are grouped into the same process group. (RSA-8912)
- Corrected "Host coverage" inconsistency in which the count of supported hosts could be less than the count of monitored hosts. (RSA-8945)
- Improved "Host coverage" percentage calculation and fixed timeframe in info icon. (RSA-8921)
- Adjusted the "Host coverage" info icon pop-up text to "Based on the last 70 minutes" (formerly "80 minutes"). (RSA-9082)
Autonomous Cloud
- The "Monitor Kubernetes / OpenShift" deployment page now references the newly released Dynatrace Operator v0.10.4. (K8S-5364)
Cluster
- Reverted strict permissions requiring users to have "settings.write" permission for manually closing problems. (DAVIS-4293)
- Fixed the case where an invalid endpoint URL format could lead to an internal server error when testing a notification in the UI. (DAVIS-4150)
- Added status property (`dt.osservice.status`) to web UI tooltip for Linux OS services monitoring. (HOST-2271)
- Fixed the IAM policy for creating calculated service metrics via multidimensional analysis. (TI-5640)
- Resolved an issue that could result in an empty trace view if a PurePath belonging to that trace contained more than one Trace ID. (TI-5823)
- Fixed an issue where a complex chart label in Data Explorer and Dashboard tile was not displayed correctly in a specific case. (EXA-5540)
- Fixed an issue where the "Update Now" button on OneAgent update settings page displayed HTTP 403 error because it required global settings permissions even when done on the host or host_group level. (PS-6957)
- Corrected enforcement of user action name length limit of 300 characters when a user action name is created with the JavaScript API `dtrum.actionName()`. (RUM-9652)
- The "Cloud platform type" property on the host page now contains the version and editions of cloud platforms whenever this information is available. (HOST-2216)
- Resolved "Host coverage" issue in which the reported number of monitored hosts was greater than the number of actually supported hosts. (RSA-8715)
- Corrected "Host coverage" to adapt the timeframe for querying the host metric to more appropriate host counts (fixes reporting an incorrect number of excluded hosts). (RSA-8961)
- Fixed an issue where exploratory Davis analysis results on entity screens would load indefinitely. (DAVIS-4308)
- This fix ensures that every process group gets its own GraphQL service assigned. (TI-5938)
Synthetic monitoring
- Corrected behavior of on-demand execution with the following conditions fulfilled: (1) On demand run, (2) Monitor failing, and (3) Monitor rerun flag set. This fix corrects the conditions for rerun: it should not be performed for on-demand executions. (SYNTH-4458)
User Interface
- Fixed an issue where application showed an error in some cases when the navigation took longer than expected. These crashes should no longer occur. (UIP-3349)
auto update
- Adjusted the version dropdown list for manual OneAgent updates on the "OneAgent updates" page to make it clearer which version of OneAgents will be updated to via the following changes: (1) remove "Latest" entry and display the specific version marked as "Latest" instead, (2) show a warning icon when a version newer than the default OneAgent installer version is selected, and (3) mark the default installer version as "Standard" and select it by default. (CLUSTER-5150)
entity query
- GeolocationType is now available as an entity selector predicate in Data Explorer. (CLUSTER-5126)
managed
- Fixed problem with displaying cluster nodes when hostname is invalid. (CLD-5894)
metric query
- Corrected Azure app services failure rate displayed in web UI. (CLUSTER-5292)
metric selector
- Fixed metric selector working incorrectly with dimension dt.entity.disk. (CLUSTER-5317)
slo
- Fixed the location header for POST endpoint. Endpoint now returns the *location* response header containing the ID of the new SLO not the url. (CA-3515)
Update 109 (Build 1.264.109)
This cumulative update contains 3 resolved issues and all previously released updates for the 1.264 release.
Component | Resolved issues |
---|---|
Cluster | 1 |
Synthetic monitoring | 1 |
User Interface | 1 |
Cluster
- Corrected information on metric calculation for custom metrics. (LIMA-7072)
Synthetic monitoring
- 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)
User Interface
- Fixed an issue where application showed an error in some cases when the navigation took longer than expected. These crashes should no longer occur. (UIP-3349)
Update 120 (Build 1.264.120)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.264 release.
Cluster
- 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)
Update 127 (Build 1.264.127)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.264 release.
Cluster
- 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 a case where very large problems could cause the entire problem manager to get stuck. (DAVIS-4587)
Update 135 (Build 1.264.135)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.264 release.
Cluster
- Automatic configuration migration for Anomaly Detection (Host) no longer overwrites Alerting/Dealerting event thresholds settings with default values. (HOST-2691)
managed
- Fixed an issue where the installation script can't run on OS with enabled FIPS. (CLD-6579)
Update 141 (Build 1.264.141)
This cumulative update contains 1 vulnerability resolution and all previously released updates for the 1.264 release.
Cluster
- Vulnerability: Resolved an issue in the configuration API in Extension Framework 1.0. (TI-6681)
Update 142 (Build 1.264.142)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.264 release.
managed
- Fixed and issue where the self-monitoring OneAgent hasn't been downloaded during installation and upgrade. (CLD-6658)
Update 143 (Build 1.264.143)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.264 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)
Update 150 (Build 1.264.150)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.264 release.
Cluster
- Resolved an issue that caused problems to become stuck in the Open state for Premium HA customers (clusters with multiple data centers). (DAVIS-4779)
- Resolved issue with failure to delete duplicate problems for premium HA, sometimes resulting in stuck open problems. (DAVIS-4345)
Update 155 (Build 1.264.155)
This is a cumulative update that contains all previously released updates for the 1.264 release.
Update 164 (Build 1.264.164)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.264 release.
es client
- Improved calculation of the average consumed disk of Elasticsearch to prevent false positive warnings about disk space consumption. (CLUSTER-7054)
managed
- Introduced a skip path verification option so Dynatrace support can handle corner cases when upgrade process cannot verify directories permissions. (CLD-7069)