To reduce the amount of data that the system must process by eliminating irrelevant traffic, use traffic inclusion/exclusion rules. The system evaluates each hit according to a combination of rules that you configure to decide whether the data is kept or discarded.
In the hosted environment, you can configure these rules in the Real User Collector component. If you are using Application Performance Management as a service, you can configure rules by modifying the rules.conf file on the Cloud Probe computer.
#Traffic section, set the value of
SYSTEM.PROPERTIES.EPX.probe.conf-collector-policies-listener-interval parameter to 0.
When you set the
SYSTEM.PROPERTIES.EPX.probe.conf-collector-policies-listener-interval parameter to a non-zero value (for example, 30), the Cloud Probe will override the contents of the probe_properties.conf file with configuration from Real User Collector every 30 seconds.
Now, the Cloud Probe uses the traffic inclusion/exclusion rules from the rules.conf file disregarding the configuration defined in the Real User Collector.
The Cloud Probe starts using traffic inclusion/exclusion rules configuration from the configuration file.
The rules configuration file must end with an empty line.
Host sweeping commands syntax for the Cloud Probe
IP sweeping commands syntax for the Cloud Probe
Configuring confidentiality policies on a Cloud Probe
Filtering traffic by using inclusion and exclusion policies