Previous Topic: Destination Statements

Next Topic: Example: Configuration Statements

Criteria Statements

If you have multiple instances of Event Management running on different computers in your enterprise, you can use criteria statements to filter messages according to attributes or content. Messages that satisfy a criteria statement are then routed to a logical Event Management destination that you specify using destination statements.

A criteria statement has the following format:

destination_name: text(text_pattern) sev(severity) [lang(language)]
destination_name

Specifies a logical identifier that matches a name configured in the destination statement file.

text_pattern

Specifies a pattern that message text must match in order to be routed to the destination. Full support is provided for wildcards using UNIX style regular expression syntax, permitting flexible message selection according to a wide range of criteria. If you do not specify a pattern, all messages are routed to the destination according to severity and language restrictions.

Note: By default, the Event Management Utilities support the syntax commonly referred to as “basic regular expression.” If you want to use the “extended regular expression” syntax, then you must use the -e start parameter to run the Event Management Utilities.

severity

(Required) Specifies the severity of messages to be routed to this destination.

Limits: INFO, WARN (warning), CRIT (critical error), IMM (immediate action), or asterisk (*) (any severity)

language

(Optional) Specifies the character-encoding scheme of the message. It represents a locale or code page name acceptable to the IBM iconv() function.

Default: Messages of all encodings are eligible for the destination.

Limits: 16 characters