We are deprecating the classic User sessions page soon and replacing it with a more powerful page for session segmentation. To stay tuned, keep an eye on our release notes.
The latest enhancement to mobile app monitoring with Dynatrace® Session Replay provides you with a movie-like replay experience of the final user actions of all user sessions that terminate in a crash. With this update, frontend developers can identify the root causes of app crashes not only on iOS but also on Android.
Dynatrace Log Monitoring is now enhanced with advanced processing, making the data locked in logs actionable and completing the observability picture on the Dynatrace platform. Easy-to-use pattern matching lets you extract any data from logs, transform and manipulate attributes, and filter or drop insignificant logs.
Log processing
Starting with Dynatrace version 1.245, Log Processing is no longer in Preview. Its capabilities are now expanded very widely to execute all kinds of log transformations on ingest with new commands and functions.
Now you can disable Service insights monitoring at an individual host level, either using a host settings page or OneAgent on a host API - Technology monitoring configuration when Service insights monitoring is enabled at the environment level.
Log ingest
Starting with Dynatrace 1.245, we extended the maximum payload size for log ingest API to 5 MB.
Problems now indicate and cross-link impacted SLOs based on the SLO entity selectors and the identified impacted.
Metrics
Prometheus Summary metric type support has been added. For existing annotated exporters, the Summary metrics are ingested by default.
Service insights
You can now disable service insights for a specific technology on selected hosts via the Dynatrace web UI and Dynatrace API when global monitoring is enabled in the Monitored technologies setting for that technology.
Go to Hosts or Hosts Classic (latest Dynatrace) and open the host details page for the host you want to configure.
On the host details page, select More (…) > Settings.
In the Monitored technologies table for that host, find the technology, expand that row, and turn off monitoring of that service on the selected host.
Memory profiling
Applications & Microservices
The memory profiling page now opens with the flame graph as the default visualization. However, if you access memory profiling from the problem page, the hotspot table remains the default visualization. It enables you to immediately understand the highest contributor. When sharing the link to a specific page, the selected view mode is persisted in the URL.
Credential vault
Synthetic Monitoring and Extensions 2.0
To access the credential vault, go to Credential Vault. It is no longer accessible via Settings.
Added management zone propagation for AWS Account (AWS_CREDENTIALS) to AWS_APPLICATION_LOAD_BALANCER and AWS_NETWORK_LOAD_BALANCER. (APM-375502)
Improved memory performance when matching alerting profiles. (APM-375614)
Correct normalization is now used for tagging rule propagation. (APM-372984)
In the Log Monitoring log viewer, selected facets are now immediately synchronized when filters change in the filter field. (APM-377496)
Resolved issue in which, when leaving a Log Viewer page, not all subscriptions were closed, leading to incorrect web UI behavior. (APM-372503)
Improved memory performance when matching and sending out problem notifications. (APM-375507)
Fixed issue with OneAgent ingest and StatsD configurations being ignored in certain situations. (APM-378053)
Session details events chart legend items are now always be displayed as required (resolves missing legend items). (RUM-4829)
Resolved issue that caused empty user session table on JavaScript error details page. (RUM-6326)
Removed specific technologies (.Net and Node.js) from gRPC switch (as it is supported for all code modules}. (APM-375480)
On the Applications > application details page, geolocations view (world map), selecting a country that never had any data no longer leads to HTTP Error 404. (RUM-6478)
Cloud Automation
Resolved issue in which orchestration project links always pointed to the Dynatrace Hub entry. (APM-378706)
OneAgent
Extended maximum payload size for Log Ingest API to 5 MB (was 1 MB). (APM-374821)
User interface
When opening the Kubernetes settings page from the Cluster details page, the settings page no longer displays the "You have unsaved changes" dialog before any user input is made. (K8S-2453)
Update 111 (Build 1.245.111)
This is a cumulative update that contains all previously released updates for the 1.245 release.
Update 127 (Build 1.245.127)
This cumulative update contains 5 resolved issues and all previously released updates for the 1.245 release.
Failure detection - request attribute conditions "equals" and "not-equals" on floating point numbers now work correctly. (APM-379472)
Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions.
Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions. (CASP-16582)
The Infrastructure Monitoring mode `--set-infra-only` OneAgent install parameter is now correctly recognized by the server. (APM-379864)
Fixed a problem that caused the "copyFromHostName" flag in rule-based service detection to be lost, causing service merging/splitting to not work as configured.
Before this fix, for an "Opaque and external web request" rule that has a {{publicDomainName}} section with {{copyFromHostName}} enabled but no {{transformations}} specified, that {{copyFromHostName}} flag would not be applied correctly (but still be shown as enabled).
In 1.244 and 1.245, if you observe the problem happening even after this fix is applied, you can mitigate it by reading and storing the rule again via the REST API. In any case this will happen automatically after upgrading to 1.246. (APM-379679)
Application Security
Resolved issue in which the "Host coverage" percentage on the "Application Security overview" page was calculated using an excessive total number of hosts, which rendered a coverage percentage that was lower than in reality. (CASP-16608)