When you set up agents to monitor your devices from different locations, you want to note the IP addresses of the locations you have chosen to monitor from. Use these IP addresses to allow traffic from the monitoring agents through your firewalls and to filter out the monitoring agents from any traffic reports or other analytics that you use. Most analytics services should allow you to specify distinct IP addresses to ignore for reporting purposes.
This way, if you use services, such as Google analytics to track the traffic on your websites, you can be sure that you are not creating false traffic from the different monitoring locations.
Depending upon your environment and devices you wish to target, you may also need to know the IP addresses in order to add them to a whitelist on a firewall to ensure the agents can reach your servers.
Here is a link to the current monitoring agent IP addresses.
What if it is not possible to use monitoring location IPs to identify traffic from Dotcom-Monitor?
To let your system know that network requests come from Dotcom-Monitor monitoring locations, we add comments to the string of the “User-Agent” request header. Thus, you can identify Dotcom-Monitor traffic by the “User-Agent” string content. The content of the comment depends on the monitoring platform type that is in use for your device:
- ServerView devices: DMBrowser/2.1 (SV)
- BrowserView devices: DMBrowser/2.1 (BV)
- UserView devices: DMBrowser/2.1 (UV)