Dynatrace SaaS release notes version 1.181

New features and enhancements

Easily measure and manage user experience with more flexible Apdex calculations
Accelerated delivery is one of the key principles of good user experience, and improved user experience leads to a better bottom line for companies. Customers enjoy using your digital channels more and buy more from your company. One recent public example is Zalando, a German retailer. By improving their load time by 100 ms, they […]
Next generation Dynatrace Davis AI becomes the default causation engine
In today’s increasingly complex environments, it’s simply impossible for a human operator to manually follow the highly dynamic nature of transactions within microservices and serverless functions. Even the best baseline approaches come with a tiny percentage of false-positive alerts, the number being directly proportional to the number of components you’re monitoring. Back during Perform 2019, […]
Latest management zone update improves collaboration for Synthetic Monitoring
Dynatrace management zones provide an effective means of collaborating across teams by enabling you to define fine-grained access control to specific segments of monitoring data. Synthetic monitors (both HTTP and browser) can be assigned to management zones based either on their names or tags. Until now, users had to have the Change monitoring settings permission […]

The .181 GA release contains 10 resolved issues.

Component

Resolved issues

Don't consider the RUM default application in application detection for browser monitors. (APM-203087)
Session replay and rage detection settings are no longer removed with configuration updates via Web Application Configuration rest API. (APM-204148)
Corrected link to Android instrumentation documentation. (APM-207338)

Fix inconsistencies in count value units. (APM-202244)
On Azure dashboard - unhealthy services were not marked red on a list of app services and functions. (APM-202734)
There might have been exception screen displayed in rare cases for .net process. (APM-203288)
Fix problem with correct identification of PaaS host. (APM-204374)
Fix scaling problem with plugin-origin charts that contain series based on the same timeseries. (APM-204486)
DB Insights, most time consuming Oracle statements - per SQL Query graphs would not match the totals displayed for this query in the table row. Graph data would be trimmed to match the UI timeframe. While the table data would match an expanded timeframe covered by the metric store. So the graphs would display less data than was summarized in a table row. The timeframe expansion performed by the metric store is a result of lowering data granularity. Eg if 1-hour granularity is available for a given timeframe and the requested timeframe would not match 1-hour slot boundries exactly, the timeframe would be implicitly expanded by the metric store to cover all the partially matching timeslots. So requesting a 1 hour 30 minute timeframe where 1 hour granularity is available 2 hours' data would be returned. (APM-196732)