Identify and Allow Monitoring Traffic

When you configure agents to monitor your devices from multiple locations, record the IP addresses of those locations.

Use these IPs to:

  • Allow monitoring traffic through your firewall
  • Exclude monitoring traffic from analytics and reports

Most analytics tools, including Google Analytics, let you exclude traffic by IP address. This prevents monitoring requests from appearing as user traffic in your reports.

If your environment restricts inbound traffic, add the monitoring location IPs to your firewall allowlist so agents can reach your servers.

Refer to the list of current monitoring agent IP addresses here: current monitoring agent IP addresses.

Identify Monitoring Traffic Without IP Filtering

If you cannot filter traffic by IP address, identify monitoring requests using the User-Agent header.

Monitoring requests include a product identifier in the User-Agent string. The value indicates the monitoring platform used:

  • ServerView devices: DMBrowser/2.1 (SV)
  • BrowserView devices: DMBrowser/2.1 (BV)
  • UserView devices: DMBrowser/2.1 (UV)

Use this value to detect and filter monitoring traffic in your systems.

Example User-Agent Headers

User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) DMBrowser/2.1 (SV)

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36 DMBrowser/2.1 (BV)

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36 DMBrowser/2.1 (UV)