TLS 1.0 and 1.1 end-of-support for RUM data

Session Replay masking v1 end-of-life

Classic user sessions page end-of-life

Log Monitoring documentation

• Log Monitoring
• Log data acquisition
• Log data analysis
• Log data alerting

• Legacy Log Monitoring v1 Documentation.
• Compare legacy Log Monitoring v1 to the latest version of Dynatrace Log Monitoring.
• Switch to the latest version of Dynatrace Log Monitoring.

Kubernetes/OpenShift monitoring setup

• 500m CPU requests
• 1000m CPU limits
• 512Mi memory requests
• 1.5Gi memory limits

Kubernetes/OpenShift workload/pod details

• Reliable detection of pods with a lifetime of less than a minute (previously, short-lived pods would sometimes be missed).
• Display of the termination status for pods that succeed (Succeeded) or fail (Failed) on their own (previously, pods would sometimes appear as Running even though they had terminated). Pods deleted while in a running state will still be displayed as Running.
• Proper linking of pod events to the pod (previously, short-lived pods would sometimes not be recognized, so the Kubernetes event would be linked to the related namespace entity instead).

Burn rate visualization for service-level objectives

Cloud Foundry transition to Settings 2.0

• For details about IAM permissions, see Manage permissions and configuration.
• For details about Settings 2.0, see Settings API.

Configuration API for AWS and Azure supporting services

Problem detection and analysis

• The Entity type filter of maintenance windows now shows both entity type ID and display name.
• You can now manage configurations of Anomaly detection for disks via Settings API—use the builtin:anomaly-detection.infrastructure-disks schema.

Extensions

• Now you can extend your observability into data acquired from an Oracle Database using SQL queries. See SQL data source.
• The display name is now required in metric metadata.

Dashboards

Synthetic Monitoring

• General Availability (Build 1.239.178)

General Availability (Build 1.239.178)

Cluster

• Vulnerability: Updated to new Marked library version for use in dashboard Markdown tiles. (APM-347587)
• Cassandra backup is deleted only after new one is ready. (APM-355433)
• Modification/deletion of disk anomaly detection rules is now applied correctly. (APM-362965)
• The attributes `nameSize` (for TileDto) and `tilesNameSize` (for DashboardDto) now correctly default to null. (APM-360685)
• In the past, ‘Monitoring unavailable’ events could have been raised for communication issues on a Dynatrace cluster even if a specific environment was not impacted. These events are now evaluated more precisely on an environment-level, so you are only notified in case your environment is experiencing a communication issue. (APM-359956)
• Corrected issue with conversion goals in the RUM web application configuration API. (APM-359797)
• Resolved issue with missing USQL query support for custom applications. It is now possible to filter custom applications with key user actions in USQL. (APM-362217)
• Generic root cause analysis rules now also consider closed events as they might explain the root cause of a problem. (APM-360327)
• You can now edit services within management zone permissions. (APM-363007)
• Fixed issue with metric selector’s :timeshift operator that led to missing timeslots. (APM-360914)
• Fixed resolution for missing tags and management zones from some entities on event and problems. (APM-361411)
• Mapped “Custom units” settings page to “Metrics” settings menu. (APM-360602)
• Corrected issue in which, when agent injection was suppressed, in some cases processes were incorrectly reported as expected to be monitored and as being monitored when calling `/api/v1/entity/infrastructure/processes` API. (APM-360446)
• Actions of renamed apps will now display waterfall analysis button whenever data is available. (RUM-4956)
• Corrected discrepancy in DDUs consumed that was displayed on consumption page. (APM-364703)
• The `Configure tile in Data Explorer` button is now in the same location as the configure button for other tiles and now is reliably displayed when a tile is selected. (APM-355105)
• Root cause relevant Kubernetes events are now correctly handled by Davis and displayed in the Problems section. (K8S-1930)
• Correct suggestions are now displayed for release product and release stage for the service filters. (APM-361736)
• Improved error handling for unexpected storage issues. (APM-360014)
• Previously activated disk analytics extension setting on environment scope is no longer considered for OneAgent after removal unless explicitly activated by host or host group. (APM-363898)
• Fixed the recently introduced rule to disable monitoring of “calico-node” processes that are not relevant to monitoring. (APM-360615)
• It is now possible to ingest all characters of the Unicode 14.0 “Supplemental Symbols and Pictographs” as dimension values via the Metrics API v2. (APM-360016)
• Total IO calculation has been corrected to no longer add asynchronous times. This may cause services to show changes in total IO times and/or alerts when used as a trigger even if the actual PurePaths did not change. (APM-359310)
• Improved metric selector filtering on entity names. (APM-363024)
• The “Exception details” link no longer crashes (404) when using a single PurePath filter. (APM-360396)
• High memory usage or potential OutOfMemory if the server is running without Elasticsearch connection for a prolonged time. (APM-362484)
• Resolved issue in which, when log events had more attributes than the allowed maximum (50 by default), sometimes the last added attributes were not the attributes cut off. (APM-356132)
• Fixed the sorting order for some Kubernetes columns: Columns that contain numbers (for example, “4 Namespaces”) are now sorted properly by count number. Previously, lexicographical sorting (1, 10, 2, 3, …) was applied. (APM-359421)

Autonomous Cloud

• The “Test connection” button in the Kubernetes settings now works properly for OCP 3.11. Previously “You are missing the get OCP Cluster Version permission” could be shown, even if the permissions were properly granted. (K8S-180)
• Fixed an issue where the Kubernetes cluster is displayed as UNKNOWN-KUBERNETES-CLUSTER-**** in custom charting. (APM-360630)
• When setting the optional Group parameter on the Kubernetes deployment page, the host group argument for the OneAgent is now set correctly. (K8S-1985)

Cloud Automation

• Corrected linking from the SLO Overview page to the Problems page (number of SLO-related problems on the SLO Overview and Problems pages now correspond). (APM-365561)