Rule Search
This Public Experimental method searches for rules across all rulesets. This method is especially useful when your organization has many rules organized in rulesets.
For example, your organization has 192,000 rules organized across 650 rulesets, and you need to know how many rules are applied for SNMP (UDP 161). You can’t easily find this information without using this method.
Note
Rule search concurrent requests are now increased to 12 searches on 2x2s and 4x2s.
Attributes for Rule Search
You can search for Workloads and IP lists by href. The ingress_services field accepts either an HREF or an object containing port/protocol/process name/service name, but not service_ports or windows_services sub-resource.
To search by providers and consumers, you can use the following attributes:
Actor Name | Actor Value Type | Required Keys | Providers (Source) | Consumers (Destination) |
---|---|---|---|---|
actors | String | N/A | True | True |
labels | JSON Object | HREF | True | True |
label_group | JSON Object | HREF | True | True |
workload | JSON Object | HREF | True | True |
virtual_service | JSON Object | HREF | True | True |
virtual_server | JSON Object | HREF | True | False |
ip-list | JSON Object | HREF | True | True |