Try it free

Exclude IP addresses and browsers from monitoring

  • Latest Dynatrace
  • How-to guide
  • Published Nov 09, 2026

With IP address and browser exclusions, you can prevent Real User Monitoring from capturing data for specific IP addresses, IP address ranges, or browsers, including bots and spiders, in your web frontends. You can also do the reverse and monitor only the IP addresses or browsers that you specify.

Exclude IP addresses

For both auto-injected and agentless frontends, you can define rules that exclude specific IP addresses or IP address ranges from Real User Monitoring. When a rule applies, automatic injection is suppressed and RUM beacons are dropped.

To create an IP address exclusion rule

  1. Go to Experience Vitals Experience Vitals > Overview.

  2. Select Web to view all web frontends.

  3. Select the frontend that you want to configure.

  4. On the Settings tab, select Open in Settings.

  5. Go to Collect and capture > Data scope and enrichment > IP address exclusions.

  6. Select Add an IP address to exclude.

  7. Enter the IP address or IP address range that you want to exclude.

  8. Optional To monitor only the IP addresses that you specified instead of excluding them, select These are the only IP addresses that should be monitored.

If your environment has uninstrumented tiers between the browser and OneAgent or the beacon endpoint on the Cluster ActiveGate, make sure that these tiers add IP address determination headers as described in Infrastructure requirements for RUM.

Exclude browsers

For auto-injected frontends, you can define rules that exclude specific browsers from Real User Monitoring. When a rule applies, automatic injection is suppressed and RUM beacons are dropped.

To create a browser exclusion rule

  1. Go to Experience Vitals Experience Vitals > Overview.

  2. Select Web to view all web frontends.

  3. Select the frontend that you want to configure.

  4. On the Settings tab, select Open in Settings.

  5. Go to Collect and capture > Data scope and enrichment > Browser exclusions.

  6. Select Add browser exclusion rule.

  7. Specify the browser, version, and platform that you want to exclude.

  8. Optional To monitor only the browsers that you specified instead of excluding them, select These are the only browsers that should be monitored.

Exclude bots and spiders

To exclude bots and spiders from Real User Monitoring, select Bots and spiders as the browser in a browser exclusion rule.

OneAgent and the beacon endpoint on the Cluster ActiveGate apply this rule without a database lookup to identify bots and spiders. Instead, they match the user agent string against a set of patterns. As a result, some traffic from bots and spiders might still be captured. To drop RUM data from bots and spiders that aren't detected this way, use OpenPipeline.

Related tags
Digital Experience