These release notes relate to Dynatrace Managed specific changes. To learn about general Dynatrace changes included in this Dynatrace Managed release, see:
Centos 6.x, Red Hat Enterprise Linux 6.x, Oracle Linux 6.x are no longer supported since October 1, 2021. However, we still maintain existing deployments and allow upgrades. We're informing you that Dynatrace Managed version 1.250 is going to be the last one that you can upgrade to on the unsupported operating systems.
Future Dynatrace Managed operating systems support changes
The following operating systems will no longer be supported starting 01 July 2025
A memory leak as been fixed in the Kubernetes module of the ActiveGate. (K8S-2964)
Application Security
Fixed absent "Detected Vulnerable Process Group" from remediation tracking page. (APM-381564)
Cluster
Resolved an issue that prevented users without "Change monitoring settings" permission from navigating to the details of a dashboard tile displaying information from a remote environment. (APM-381194)
Fixed inadvertent enablement of pre-release versions of Application Protection feature on agents if globally enabled. (OA-6239)
Modified formatting for percent and promille units in metric explorer. (EXA-2153)
Tiles on a dashboard are periodically not displayed. (EXA-2140)
Rest API: changing capturingName of metaDataCaptureSettings doesn't work. (RUM-6922)
synthetic
Fixed credential fields being enabled before clicking *Overwrite credential*. (SYNTH-2352)
Update 186 (Build 1.246.186)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.246 release.
Cluster
Fixed an issue with metric query parallelization that caused doubled values when reading a volatile time series (unconsolidated datapoints). (CLUSTER-2416)
Update 191 (Build 1.246.191)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.246 release.
Cluster
Resolved issue with incorrect default baselining settings for alerting, which resulted in incorrect baseline calculations and no alerting. (DAVIS-1788)
Introduced validation for management zone settings that prevents configuring more than one metric key condition for the same dimensional rule. (APM-383118)
Update 192 (Build 1.246.192)
This cumulative update contains 36 resolved issues and all previously released updates for the 1.246 release.
Expanding a resolved security problem in the third party vulnerabilities list now shows the details. (CASP-16501)
Cloud automation solution
Fixed an issue where the Orchestration Page would throw an unexpected error when loading the CA-instance URLs. (APM-379341)
Cluster
Error Count filter can no longer be applied if it has already been applied. (APM-368957)
Added management zone propagation for AWS Account (AWS_CREDENTIALS) to AWS_APPLICATION_LOAD_BALANCER and AWS_NETWORK_LOAD_BALANCER. (APM-375502)
Fixed an issue in which world maps were not visible in anonymously shared dashboards. (RUM-6724)
In the Log Viewer, improved display of facets loading indicator (indicator shown only when using search input, not on result fetching). (APM-377465)
Resolved an issue that prevented users without "Change monitoring settings" permission from navigating to the details of a dashboard tile displaying information from a remote environment. (APM-381194)
Resolved issue (introduced in Dynatrace versions 243 and 244) that inadvertently disabled Log Source configuration updates for OneAgents that were connected to server nodes added after upgrade of a cluster. (APM-380889)
Fixed an issue with the 403 errors that some customers could get on the Host page. (APM-379830)
Fixed an issue with rule-based service detection: 'Between' and 'ReplaceBetween' transformations now work correctly in all circumstances. (APM-381261)
Resolved issue with incorrect default baselining settings for alerting, which resulted in incorrect baseline calculations and no alerting. (DAVIS-1788)
Introduced validation for management zone settings that prevents configuring more than one metric key condition for the same dimensional rule. (APM-383118)
Fixed cluster upgrade to version 1.246.191 (was failing with "Nodekeeper was not upgraded successfully" message). (APM-383763)
Fixed an issue in which alerting profiles containing multiple rules with the same severity but different duration and tag filters matched problems erroneously, sending out notifications that shouldn't have been sent. (DAVIS-1966)
Improved memory performance when matching alerting profiles. (APM-375614)
Fixed the OpsGenie integration for problem close notification. (APM-379633)
Correct normalization is now used for tagging rule propagation. (APM-372984)
In the Log Monitoring log viewer, selected facets are now immediately synchronized when filters change in the filter field. (APM-377496)
Configuration changes via REST API using a non-personalized token are now audited with the public token identifier instead of the user who created the token. (APM-371592)
Attempting to delete a failure detection parameter that is already in use by a failure detection rule returns an appropriate constraint violation message and prevents the operation. (APM-376691)
When opening the Kubernetes settings page from the Cluster details page, the settings page no longer displays the "You have unsaved changes" dialog before any user input is made. (K8S-2453)
Fixed an issue causing events on `Requests to unmonitored hosts` services (and other grouping services) to merge (which they should never do). (APM-377546)
The option to create a memory dump is now available for .NET processes directly from the process page. (TI-1745)
Fixed missing environment metadata in properties on new host screen. (APM-376340)
Improved memory performance when matching and sending out problem notifications. (APM-375507)
The JavaScript error details page now displays the full file blob URL instead of just the last segment of the URL. (RUM-6440)
Resolved issue in which, when leaving a Log Viewer page, not all subscriptions were closed, leading to incorrect web UI behavior. (APM-372503)
Breadcrumbs on service-related settings pages now show correct information. (APM-376862)
Full web service detection rules: fixed the Context Root - URL segments copying transformation. (APM-376414)
Removed specific technologies (.Net and Node.js) from gRPC switch (as it is supported for all code modules}. (APM-375480)
Session details events chart legend items are now always be displayed as required (resolves missing legend items). (RUM-4829)
Fixed cluster upgrade to version 1.246.191 (was failing with "Nodekeeper was not upgraded successfully" message). (APM-383763)
Cluster Management Console
Environment name length is now correctly validated upon creation. (APM-374428)
Infrastructure monitoring solution
Due to security concerns, we have blocked custom SQL extensions using the Extensions 2.0 framework. (APM-378722)
Log Monitoring
Extended maximum payload size for Log Ingest API to 5 MB (was 1 MB). (APM-374821)
User Interface
Improved refreshing access tokens table to represent latest state in the server database after using a pagination. (APM-377338)
Update 203 (Build 1.246.203)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.246 release.
Cluster
Resolved issue in which the alerting configs with parent-aware filters (for example, MANAGEMENT_ZONE filter on SERVICE_METHOD) were considered invalid and not processed by the alerting engine. (DAVIS-2112)
Fixed an issue with some OneAgent-raised events, for example, high CPU, being auto-closed after 6 hours, even if the underlying issue still persists. This could also cause problems to be closed early when all of their events get auto-closed too early. (DAVIS-2324)