Dynatrace SaaS release notes version 1.173

New features and enhancements

Support changes

Dynatrace no longer supports connections that are encrypted with TLS versions 1.0 and TLS 1.1. This is due to security vulnerabilities present in these versions. We don't expect this to have a significant impact on customers as the traffic we receive is almost universally industry-standard TLS 1.2. However, this change may impact customers who still use Internet Explorer 11 to access the Dynatrace Web UI, or customers who use a legacy HTTP client to integrate with Dynatrace REST API.

Resolved issues

General Availability (Build .173)

The .173 GA release contains 37 resolved issues.

Component
Resolved issues
4
3
29
1

Code-Level

  • Cannot create web request naming rule based on existence of confidential request attribute. (APM-183100)
  • Two queues from same vendor and with the same display name are wrongly created as separate queues. (APM-183521)
  • Default limit for supported number of different message queues is too low. (APM-183615)
  • Request Attribute Argument Capturing UI: The wrong element was selected when reopening a data source. (APM-185567)

Session Replay

  • Accessing Session Replay site from IE gives a TDP. (APM-183687)
  • Pointers for load events in the timeline are misplaced on top of user interactions. (APM-182221)
  • Clicking and replaying a session before closing extension message leads to TDP. (APM-184078)

Cluster

  • Can not save User-Agent value while configuring HTTP monitor. (APM-181229)
  • Odd UI behavior when setting the value of the global setting for Infra memory usage. (APM-180907)
  • We have wrong label for ec2 machines. It was AWS Elastic Container Service instead of AWS Elastic Compute Service. (APM-182008)
  • Firefox - tooltips on infographic not showing up. (APM-182009)
  • Old network overview - nic/pgi list is not filtered by management zone. (APM-182335)
  • In special case, when two plugins creates the same group of chart we may create a single chart with series from two different plugins. (APM-182657)
  • On Network overview page, appears a filter even though we have no monitored networks. (APM-182814)
  • Deployment status filter: inconsistency of operating system name 'linux' vs. 'Linux' (upper / lower case). (APM-183150)
  • Technology tiles - affected instances not displayed correctly. (APM-183968)
  • zLinux agent install command line contains parameter that is not valid for this platform. (APM-184354)
  • Filter bar suggestion incorrectly positioned after deleting a filter. (APM-177148)
  • Demo state incorrectly set when switching screens through a dashboard. (APM-176964)
  • Missing "Process group" label in the global search on some screens. (APM-182133)
  • Oracle DB Insights: Configurations were not visible when configuration entries with the same fields were added. (APM-183675)
  • USQL: Selecting useraction.navigationStart and grouping by useraction.navigationStart leads to empty results. (APM-184069)
  • Specific USQL query returns the fully qualified Java class in the user-visible response. (APM-182883)
  • Customer is unable to change the sensitivity for Anomaly detection on service RentalAgreement. Possible UI Bug. (APM-182527)
  • Not being alerted on problems. (APM-182316)
  • Fixed notification bug that if a problem was already notified to an integration and a new event correlated into the problem afterwards which is part of a maintenance window which is configured to suppress problem creation/alerting, no resolved notification would be sent out and problems would forever stay open in stateful integrations (e.g. PagerDuty, OpsGenie). (APM-182919)
  • AWS initial connection test is now checking all regions in partition. (APM-182129)
  • Users which have a very large number of Management Zones assigned may have issues sharing dashboards. (APM-172801)
  • Dashboard sharing: Sharing cannot be disabled if sharing token cannot be created. (APM-182130)
  • Single host view response time regression. (APM-182957)
  • ActiveGates before sprint 154 may cause performance impact on cluster nodes if the cluster has a very large number of API tokens. (APM-183401)
  • Previously available token permissions are no longer possible to assing in the token REST API. (APM-183782)
  • Default behavior of the VMware monitoring flag of old Environment ActiveGates corrected: AGs < Sprint 100 now have the flag "on" as default AGs >= Sprint 100 act as configured by the customer. (APM-181908)
  • Improved Agent HEAD request handling in ActiveGates: Previously the ActiveGate defaulted to a valid 204 if an Agent sent a HEAD request due to the missing server information on the Http request. ActiveGates now check if at least one server is reachable to return a valid 204. This improves re-connection of agents if the ActiveGate has network connectivity problems (as in this case where the ActiveGate had a problem with certificate resolution due to missing certificate store). (APM-182700)
  • The introduction of a quality of service control mechanism in release 170 introduced an unexpected thread pool bottleneck that temporarily blocked the Cluster REST API endpoints under very heavy load scenarios for one particular customer. Data ingest from agents was not affected and therefore no data was lost during that timeframe. The original default values have been restored. (APM-183527)
  • A new PHP Agent flag was introduced which can lead to an agent crash if sent to PHP agents with a version older than Sprint 171. The cluster now handles this case and skips the flag for older agents. (APM-184726)

Log Analytics

  • Host id information is missing for docker container logs. (APM-181651)