Starting with April 2022, Dynatrace is retiring TLS 1.0 and TLS 1.1 for Dynatrace SaaS RUM data.
Starting with Dynatrace version 1.240, Session Replay masking v1 will no longer be supported. If your application uses the RUM JavaScript version 1.192 or earlier, you must update the RUM JavaScript to at least version 1.193 to enable masking v2. Otherwise, Session Replay will stop working once Dynatrace version 1.240 is live.
We are deprecating the classic User sessions page soon and replacing it with a more powerful page for session segmentation. This will happen with Dynatrace version 1.239 or later. To stay tuned, keep an eye on our release notes.
Starting with OneAgent 1.237, log file rotation patterns support a rotation identifier that doesn't have to be surrounded by any of the following characters:
.
_
-
(
)
[
]
Detected log files
Recognized rotation pattern
/var/log/access20220322.log
/var/log/access20220315.log
/var/log/access20220308.log
/var/log/access#.log
/var/log/access.20220322.120000Z.log
/var/log/access.20220322.090000Z.log
/var/log/access.20220322.060000Z.log
/var/log/access.#.#Z.log
Because of this change, some of the log files that were autodicovered by previous versions of OneAgent (OneAgent version 1.236 and earlier) may change their name. This may require adjustments in Log Monitoring settings such as:
dt.kubernetes.workload.kind
, dt.kubernetes.workload.name
, and dt.kubernetes.cluster.name
dimensions have been added, while k8s.<controllertype>.uid
and k8s.<controllertype>.name
have been removed.builtin:cloud.kubernetes.pod.containers
and builtin:cloud.kubernetes.pod.desiredContainers
are updated for scalability reasons. The pod (and also the node) dimension are removed from these metrics. In return, three container metrics were added to the charts on the workload details page. The impact of this change to existing dashboards and custom alerts is described in the Q&A post.Deprecated fraction-based aggregations (OF_INTEREST
, OTHER
, OF_INTEREST_RATIO
, OTHER_RATIO
) reach end of support. Metric event configurations using one of those aggregations will be disabled.
Maintenance windows now support filtering based on generic entity types.
We improved the existing DDU consumption overview page formerly available at Settings > Accounting > Davis data units overview and moved it to Account Management > License / Subscription > Overview > Davis data units. The new page offers a clearer overview with the additional functionality to group metrics consumption into a tree structure for easier drill-down analysis.
These previously existing settings are now available to be used in security policies:
Settings > Monitoring > OS services monitoring Settings > Preferences > Network zones settings Settings > Preferences > Data privacy > Session Replay Settings > Web and mobile monitoring > Capturing > Resource capture for Session Replay Settings > Web and mobile monitoring > Web applications > Enablement and cost control Settings > Web and mobile monitoring > Mobile apps > Enablement and cost control Settings > Web and mobile monitoring > Custom applications > Enablement and cost control
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.237.
The 1.237 GA release contains 22 resolved issues.
Component | Resolved issues |
---|---|
Cluster | 18 |
Dynatrace API | 1 |
Infrastructure Monitoring | 1 |
Synthetic monitoring | 1 |
User interface | 1 |