Dynatrace SaaS release notes version 1.184

New features and enhancements

Your action required Add newly added public IP addresses to the allow list

In the first week of March 2020 we will replace public IP addresses that are used by Dynatrace SaaS to send out Dynatrace-detected problem notifications. If you've defined a firewall rule to allow incoming alerts from the Dynatrace public IP addresses, please add the newly introduced public IP addresses to your URL allow list.

The change in IP addresses will take place in the first week of March 2020! To avoid an alert outage, you must add the new IP addresses to your firewall allow list before March 2020.

AWS region Current public IP addresses New public IP addresses

North Virginia [us-east-1]


Oregon [us-west-2]


Ireland [eu-west-1]


Sydney [ap-southeast-2]


Resolved issues

14 total resolved issues (2 critical issues)

Component Resolved issues
Code level analytics 1
Log monitoring 1
Cluster 9 (2 critical)
User Interface 3

Code level analytics

  • For a given list of request naming rules it is now guaranteed that always the first completely matching rules renames the request (APM-211692)

Log monitoring

  • Improved validation of search queries in Log Viewer. (APM-207256)


  • Fixed presenting wrong data (from previously visited host) in System Load and Physical CPU headers on Host's details screen. (APM-208952)
  • Fix incorrect number of AWS Supporting services with problems on AWS dashboard's infographic (APM-211212)
  • Affected entities are now correctly counted in Network Overview's environment details (APM-211296)
  • Memory usage merging for restarted processes for PaaS hosts on host list is limited to 1000 processes (APM-216884)
  • Fixed missing Network Interfaces in Network Overview with applied Management Zone (APM-217385)
  • Enable USQL queries with combinations of PERCENTILE and FILTER (APM-209178)
  • Critical issue: Screens may fail to load on a Managed Environment when internal network requests are very slow. (APM-210777)
  • Enable table USERERROR when using REST API to execute USQL queries (APM-210805)
  • Critical issue: During the update from Sprint 183 to Sprint 184 it was possible in rare cases that internal migration code caused an endless loop which consumed all webserver threads in the thread pool causing a server becoming unresponsive. (APM-217530)

User Interface

  • Fixed tiles with a custom timeframe not being refreshed (APM-210133)
  • Fixed an issue when the management zone selector was not visible for users with tenant permissions (APM-210254)
  • Fixed issue when switching the timeframe from last 24 hours to previous and next 24 hours at midnight led to a last 5 minutes time frame (APM-211028)