We have vulnerability scanning tools and load balancer heartbeats that cause errored or useless one node purepaths that we would like to exclude globally rather than creating a measure in each profile to apply to each BT. That would be quite tedious. DCRUM has the ability to specify client IPs/ranges to exclude from AMD processing. I was hoping to find something similar in AppMon.
In the web requests sensor settings (or servlet sensors) for the relevant agent groups in the system profiles you can add excluded web requests to stop PurePaths from being created from them. That's what we normally use to exclude probes and hearbeat checks etc...
There's no way to exclude IPs or ranges directly, the technology is very different from how DCRUM works.
Thanks, but that solution only works if you know the specific URI not client IP. That will likely work for heartbeats, but not for vulnerablility scans where the URI is, for the most part, unknown.