Using Wildcards to Represent PATROL Instance Names
When you set up parameter threshold or poll time rules, you may want to create one rule that matches several PATROL instances. For example, you may want to create a parameter threshold rule for any process that contains the letters WIN. You can do this using wildcards.
PATROL KM for Event Management uses the following set of characters to identify a wildcard: {re:*}.
For more information, see the following example.
Wildcard Usage | Matches | No Match |
---|---|---|
CPU_{re:*} | CPU_03 | CP_1 |
Requirements for Using Wildcards
The following usage rules apply to wildcards:
- You can use wildcard only when the processWildcards configuration variable is enabled.
- You can use a wilcard only to represent PATROL instance names. You cannot use wildcards to represent host names, parameter names, or any other PATROL object.
- You can use wildcards only in threshold and poll time rules. You cannot use wildcards in notification rules.
- You can use only one wildcard in an expression.
- You cannot use wildcards to specify the beginning or ending of an instance name. For example, CPU_{re:*} matches both HoustonCPU_03 and CPU_03.
- Rules that use explicit instance names take precedence over rules that contain wildcard matches.
- Rules that contain wildcard matches take precedence over rules that use the __ANYINST__ variable to represent any instance name.
For more information, see the examples shown in the following table.
Wildcard Usage in Threshold Rules: Examples
Processes | Rules | Result |
---|---|---|
| Rule #1: | Since rule #2 did not match any of the processes running on the host, rule #1 is applied to all of the instances on the host. |
| Rule#1: | Since rule #1 is an exact match for a process that is running on the host, it takes precedence over rule #2. |