Dynatrace Managed release notes version 1.242
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
Maximum user actions per minute limit
We increased the maximum user actions per minute limit to 50,000 for all new environments.
For existing environments, you can still configure this limit at Cluster Management Console > Environments in the Cluster overload prevention settings section.
Application Security and Dynatrace Premium High Availability
Starting with this release, you can use Application Security on Dynatrace Premium High Availability clusters.
Cluster Management Console improvements
We've added additional section descriptions to the Environment Details page in Cluster Management Console to display monthly and annual quota timeframes more clearly.
Operating systems support
Current Dynatrace Managed operating systems support changes
The following operating systems will no longer be supported starting 01 November 2024
- Linux: Oracle Linux 9.0, 9.3
- x86-64
- Vendor announcement
- Last compatible version: 1.302
- Linux: Rocky Linux 9.0, 9.3
- x86-64
- Vendor announcement
- Last compatible version: 1.302
Past Dynatrace Managed operating systems support changes
The following operating systems are no longer supported since 01 July 2024
- Linux: Amazon Linux AMI 2018.x
- x86-64
- Vendor announcement
- Last compatible version: 1.290
The following operating systems are no longer supported since 01 August 2024
- Linux: Oracle Linux 8.9
- x86-64
- Vendor announcement
- Last compatible version: 1.292
The following operating systems are no longer supported since 01 October 2024
- Linux: SUSE Enterprise Linux 15.2
- x86-64
- Vendor announcement
- Last compatible version: 1.300
Resolved issues
General Availability (Build 1.242.186)
The 1.242 GA release contains 38 resolved issues.
Application Security
- Connectors in the vulnerability attack path visualization are now displayed correctly. (CASP-14457)
Autonomous Cloud
- Test connection button for CloudFoundry settings and Kubernetes cluster settings pages is now disabled for users with missing `settings:write permissions`. Otherwise users could run into 403 pages. (K8S-1995)
- Default values are now used when adding new rules at the Cloud application and workload detection settings where updated. (APM-368443)
Cloud automation solution
- A `%` sign in SLO title no longer causes `An error occurred` in SLO tile. (APM-370516)
Cluster
- Applied correct labels to the New User filter suggestions. (APM-365683)
- Resolved an issue in which the export of a user session could lead to user sessions being exported multiple times. (APM-370258)
- Resolved an issue with settings for automatically applied tags that prevented editing persisted values if the rule count for a single tag was already over the currently defined rule limit. (APM-373253)
- Fixed an edge case where JavaScript error origin was wrongly determined. (RUM-5580)
- The container restart chart on the Kubernetes workload details page has been corrected. (In some cases, the chart showed erroneous spikes.). (K8S-2070)
- Fixed an issue in which the preview for User action naming rules did not work when adding multiple rules. (APM-364822)
- Migrating custom charts to Data Explorer charts now works for custom charts containing metrics created from the Rest API before version 1.178. (APM-367699)
- The filter component now uses a default data source when none is available. (APM-366531)
- The "Show related trace" link in log details now uses a 10-minute timeframe. (APM-361250)
- Resolved an issue with a slowdown in the Events v1 API. (APM-366217)
- Resolved broken links in Markdown tiles. (APM-371433)
- Resolved issue in which, using the new Settings 2.0 Custom IP mapping configuration, a mapping that only resolved to the region (not city) would not be recognized. (RUM-5988)
- Enables the background migration of OneAgent settings (v1 to v2) regardless of any constraint so that existing settings will be persisted as they are. (APM-371980)
- Corrected link for "Deep monitoring" settings of process groups. (APM-367799)
- Fixed issue that prevented the creation of a calculated service metric for a specific service ID. (APM-367310)
- Users are once again able to create new sessions and user action properties of type request attribute from the web UI. (RUM-5315)
- Fixed an issue with missing data for network TCP metrics on the new host page. (APM-367774)
- Resolved issue causing unusable mobile provider page in some cases when rewrite rules were used to remove the protocol of web request URLs. (RUM-5788)
- Text in the content column of the log viewer is no longer truncated. (APM-366198)
- Fixed a problem in which the RUM application configuration could not be stored. (RUM-5677)
- Fixed an issue, in which users without global permissions were not able to see ingested traces related to services they had permissions to view. (APM-367818)
- Removed the loading overlay when querying/selecting facets. (APM-368050)
- Fixed a bug in the "RUM - JavaScript tag management" API related to the latest version of OneAgent JavaScript library. (RUM-5698)
- The monitoringDataPath of auto-injected applications can now be reset to null via the Configuration API. (RUM-5622)
- Reintroduced a limit of 100,000 process group instances (last 72h) running on hosts presented on the "Deployment status" page for OneAgents. (APM-370529)
- In ServiceNow notifications, missing metric information is now provided (metric selector is exposed as `metricName`). (APM-367922)
- Fixed a problem with cross-environment tracing when an URL with a trailing slash was configured. (TI-81)
- Fixed problem with Cassandra JMX password synchronization. (APM-373473)
- Fixed an issue in which web service detection rules didn't apply as configured for rules using segmentsToCopyFromUrlPath in contextRoot. (APM-373214)
- Resolved an issue that prevented mobile apps from switching on and off using the configuration UI. (APM-371139)
- Fixed issue that caused a 503 error on the new host page after 15-20 seconds. (APM-371797)
Cluster Management Console
- Fixed the displayed date of the last Elasticsearch backup. (APM-367395)
- Regular expressions in settings for automatically applied tags are no longer validated for ECMAScript compatibility (to avoid rejecting previously accepted expressions as invalid). (APM-373249)
Infrastructure monitoring solution
- Restored display of missing EEC self-monitoring metrics. (APM-369870)
Update 190 (Build 1.242.190)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.242 release.
Cluster
- Fixed inconsistency in merging of problems. (APM-372339)
Update 201 (Build 1.242.201)
This cumulative update contains 2 resolved issue (including 1 vulnerability resolution) and all previously released updates for the 1.242 release.
Cluster
- Vulnerability: Implemented cross-site scripting (xss) vulnerability fix. (APM-373905)
Cluster Management Console
- Fixed issue that delayed rollout of new "Disk options" settings page for some environments. (APM-374499)
Update 202 (Build 1.242.202)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.242 release.
Cluster
- Prevent evaluating root cause entity management zones and tags in problems which in some cases led to spam alerts. (DAVIS-1795)
Cluster Management Console
- Fixed possible backup stuck in pending state when a node was removed. (APM-375115)
Update 204 (Build 1.242.204)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.242 release.
Application Security
- Resolved issue in which the "Host coverage" percentage on the "Application Security overview" page was calculated using an excessive total number of hosts, which rendered a coverage percentage that was lower than in reality. (CASP-16608)
Update 205 (Build 1.242.205)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.242 release.
Application Security
- Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions. Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions. (CASP-16582)