- Action Analytics
- AppExpert Applications and Templates
- Entity Templates
- HTTP Callouts
- Pattern Sets and Data Sets
- Policies and Expressions
- Rate Limiting
- String Maps
- Rate Limiting at the Packet Level
- URL Sets
Policy expressions for string matching operations on a large set of string patterns tend to become long and complex. Resources consumed by the evaluation of such complex expressions are significant in terms of processing cycles, memory, and configuration size. You can create simpler, less resource-intensive expressions by using pattern matching.
In many cases, you can use either pattern sets or data sets. However, in cases where you want specific matches for numerical data or IPv4 and IPv6 addresses, you must use data sets.
To use pattern sets or data sets, first create the pattern set or data set and bind patterns to it. Then, when you configure a policy for comparing a string in a packet, use an appropriate operator and pass the name of the pattern set or data set as an argument.