Dynatrace SaaS release notes version 1.239
- Dynatrace boosts Synthetic Monitoring with auto-synchronized credentials from external vaults
Dynatrace has introduced a convenient and secure way of integrating Dynatrace synthetic monitors with external secret vaults such as HashiCorp Vault and Azure Key Vault. With this new feature, Dynatrace synthetic monitors can monitor websites and API endpoints protected with credentials stored in these external vaults without requiring additional effort from the teams responsible for managing the monitors and credentials.
TLS 1.0 and 1.1 end-of-support for RUM data
Starting with April 2022, Dynatrace is retiring TLS 1.0 and TLS 1.1 for Dynatrace SaaS RUM data. For more details, see 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
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.242 or later. To stay tuned, keep an eye on our release notes.
Distributed tracing powered by PurePath Technology®
We are improving the Dynatrace web UI to use the term Distributed traces consistently across all pages, in the same way it is already used in the Dynatrace menu. With the current iteration, all PurePath drilldown links have been renamed to Distributed traces.
New features and enhancements
Log Monitoring documentation
Starting with Dynatrace version 1.239, we have restructured and enhanced our Log Monitoring documentation to better focus on concepts and information that you, the user, look for and need.
- Log Monitoring
- Log ingest & process (Logs Classic)
- Log data analysis (Logs Classic)
- Log data alerting (Logs Classic)
If you still use the legacy version of Log Monitoring (Log Monitoring v1), the Log Monitoring v1 documentation is still available, but we strongly encourage you to switch to the latest Dynatrace Log Monitoring version and gain direct access to the log content of all your mission-critical processes. You can create custom log metrics for smarter and faster troubleshooting, and you will be able to understand log data in the context of your full stack, including real user impacts.
- 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
dynakube.yaml file now comes with default ActiveGate resource limits:
These limits are designed to prevent ActiveGate startup process slowdown and excessive node resource usage. The default values cover a large range of different cluster sizes; you can modify them according to your needs, based on the ActiveGate self-monitoring metrics.
Kubernetes/OpenShift workload/pod details
Improved the way Dynatrace processes ActiveGate Kubernetes pods:
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
Runningeven though they had terminated). Pods deleted while in a running state will still be displayed as
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
You can now enable a burn rate visualization during SLO creation either from the SLO wizard or from Service-level objective definitions by enabling Burn rate visualization enabled. Based on the values of the slow-burn and fast-burn thresholds, a yellow or red error budget burn rate symbol is shown in the Error budget column of an SLO on the Service-level objectives page, indicating whether the SLO is exceeding one of the thresholds.
Cloud Foundry transition to Settings 2.0
You can now use IAM policies for fine-grained user permissions.
- 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 cloud 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
- 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.
Data explorer and dashboards
- You can export from the Data explorer to a CSV file. For details, see Data explorer.
- The Metric and dimension usage + rejections dashboard preset is now available.
When you set up synchronized username-password pairs in the credential vault, Dynatrace automatically creates HTTP monitors specifically for the purpose of synchronization. You can also use the new
api.saveCredential() method in pre-and post-execution scripts to create your own synchronization monitors.
Settings security policies
These previously existing settings are now available to be used in security policies:
- Settings > Anomaly detection > Hosts
- Settings > Anomaly detection > Disks
- Settings > Anomaly detection > Custom disk-detection rules
- Settings > Anomaly detection > AWS
- Settings > Anomaly detection > VMware
- Settings > Cloud and virtualization > Cloud Foundry
- Settings > Preferences > OneAgent features
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.239.
General Availability (Build 1.239.178)
The 1.239 GA release contains 32 resolved issues (including 1 vulnerability resolution).
- 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)
- 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)
- 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)