Alerting is a crucial aspect of monitoring your web application. Alerts warn you when your web application doesn't meet performance standards so you can respond quickly and fix the issue. To scale up and further guarantee the delivery of all your Dynatrace alerts, we're adding new public IP addresses.
Please note that this configuration change will affect all our Dynatrace public alert notification IP addresses.
Your action is required: Add new public IP addresses to Allow list
Action required: If you’ve defined a firewall rule to allow incoming alerts from the Dynatrace public IP addresses, please also add our newly introduced public IP addresses to the firewall rule.
Am I affected?
This configuration change affects all Dynatrace SaaS users who’ve configured any alerting channel in Dynatrace other than email (which isn’t affected).
When will the change be effective?
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.
What can happen if I don’t change my firewall configuration?
If you don’t add the new Dynatrace public IP addresses to your firewall, all incoming Dynatrace alerts will be blocked by your own firewall.
Ok, what should I do?
To be on the safe side, simply add the current as well as the newly introduced public Dynatrace IP addresses for your environment region to your firewall’s allowed addresses list.
Current public IP addresses
Currently, Dynatrace uses the following public IP addresses in the different AWS regions to send out notifications to your systems whenever a problem is detected:
North Virginia [us-east-1]:
Newly added public IP addresses (these will replace the current ones for each region)
North Virginia [us-east-1]
Additional ways we’re announcing this news
This important message is also shown within in-product notifications for all environment admins, sent out to your Dynatrace One representative, and reported in advance in our regular release notes.