Dynatrace allows you to exclude specific IP addresses, browser types, robots, and spiders from Real User Monitoring.
You cannot block traffic generated by Dynatrace synthetic monitors using the settings described below. In particular, excluding the IP addresses of Synthetic locations as well as excluding bots and spiders will not block Synthetic Monitoring traffic.
While you can dissociate manually assigned applications from synthetic monitors, you cannot dissociate auto-assigned applications from synthetic monitors.
To exclude the Synthetic data from your analysis, leverage the User type: Real users filter available for most application details pages, Data Explorer, session segmentation, USQL, and more.
In your application settings, you can exclude a single IP address or an IP address range.
To exclude an IP address
If you want to exclude certain outdated browser types from your list of monitored browsers, create browser exclusion rules.
To create a browser exclusion rule
Your monitored application might encounter traffic generated by automatic bots or spiders. This traffic might trigger Unexpected low traffic alerts that make it difficult to see any relevant issues. You can exclude bots and spiders from RUM.
To exclude bots and spiders from RUM
It takes a few minutes for your changes to update all OneAgent instances.
Unlike the classification of users that Dynatrace adds to captured RUM data, this feature doesn't rely on database lookups, since it's applied by OneAgent. Instead, the user agent string is matched against a set of patterns, which is not as precise as a database lookup. For this reason, some traffic from bots and spiders might still be captured.