Dynatrace introduces new enhancements to application problem analysis that allow I&O teams to identify and prioritize issues such as crashes and errors in the problem view. These enhancements add enriched context that help explain not just the “what” but also the “why” behind the issues so that DevOps teams can take corrective action based on reliable AI-driven answers rather than basic monitoring data.
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.
AppMon reaches end of life on March 31, 2022. With that, we're deprecating integration between Dynatrace and AppMon, and it is no longer possible to push AppMon's data to Dynatrace.
NAM reaches end of life on March 31, 2022. With that, we're deprecating integration between Dynatrace and NAM, and it is no longer possible to push NAM's data to Dynatrace.
The minimum length of metric keys submitted via the ingestion protocol is 3 characters.
The averaging of numeric values is now supported for session properties.
Each SLO is represented by two metric queries. When you create an SLO, you can now configure these metric queries by entering a Metric name. For details, see Configure a service-level objective.
Dynatrace now supports monitoring for Azure Database for PostgreSQL - Flexible Server.
Cloud application and workload detection now provides better support for your release strategies in Kubernetes. For details, see Cloud application and workload detection.
This feature requires OneAgent version 1.237+.
Also you can now manage configurations via Settings API—use the builtin:process-group.cloud-application-workload-detection schema.
In Data Explorer, per metric, you can now use the Format setting to determine whether Dynatrace automatically formats the selected metric.
OneAgent version 1.237+
You can now monitor the availability of key processes on your hosts. For more information, see Process availability.
OneAgent version 1.237+
The Process instance snapshots section of the new host overview page offers additional insights into the most resource-consuming processes running on your host and the processes defined for process availability monitoring. For more information, see Host monitoring with Dynatrace.
You can now manage configurations of IBM MQ monitoring via Settings API—use the builtin:ibmmq.ims-bridges, builtin:ibmmq.queue-sharing-group, and builtin:ibmmq.queue-managers schemas.
These previously existing settings are now available to be used in security policies:
OpenTelemetry spans ingested via the trace ingest API now produce services in Dynatrace. Dynatrace uses the OpenTelemetry span resource attribute service.name to create services. You need to add the attribute via OpenTelemetry instrumentation. For more information, see OpenTelemetry and Dynatrace.
With this new feature:
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.238.
The 1.238 GA release contains 16 resolved issues.