User guide

Setting Up Fault Management Configuring Event Parsers
920
AlliedView NMS Administration Guide
9.4.2 Setting Event Parsers
Select an Event Parser from the list to see how the fields are configured for that Event parser. The following table describes
these fields at a general level, as well as the option buttons. Many of the fields will have a variable name, discussed after this
table.
TABLE 9-4 Event Parser Configuration Form
Option Description
Name Name of the event. The name should match the type of event.
Match String
The match criteria determine whether the Event will be parsed by the given Event parser or not. If a
field is left blank, it is automatically matched. Otherwise all fields (AND condition applied) must
match the input event.
To specify a match criteria, the following may be used in expressions.
Wild Card - Asterisk (*): To signify match 0 or more characters of any value. e.g., *Failed* will match
any String with Failed somewhere in it.
Negation - Exclamation (!): This can be used at the start of a field, to specify exclusion of Events
matching the succeeding expression. e.g., !Failed will exclude Strings with Failed anywhere in them.
Note: Expressions like *Failed, Fai*d and * have the expected meanings in the match criteria.
Tokenizer
String
Allows you to break up the input field into a series of tokens that can then be used in the output
Event object. The tokenizer definition is a string with the tokens represented by $1, $2, etc. Only
positive integers are allowed following '$'.
Example:
Consider the case, where you expect an event message text string as:
Line Card 31 failed on Shelf 54: No Response - (Match String).
The Line Card Number (31) and the Shelf Number (54) may be required while defining other
properties of event, so they will be tagged as tokens with a token number.
Line Card $1 failed on Shelf $2: No Response - (Tokenizer String).
After such tokenization, the token number is used in the output event definition. Specifying $text$1
for any field in the output event definition will be replaced with the value 31, while specifying
$text$2 will be replaced with 54.
Note: To identify the Replaceable parameter of a specific field, the token number should be
preceded by the field, for example $text$1 indicates the first tokenized string of the field
Message.
The tokens of any field can be used in any other field, provided this Note is followed.