User guide

Setting Up Fault Management Configuring Event Parsers
921
AlliedView NMS Administration Guide
Output String
The output of the event parser is an Event object, which will be the modified instance of the
incoming event. The attributes of the Event object are defined by what are specified in the event
parser, so it is necessary to select correct values for important attributes such as failure object
(affected Entity), severity, and message text.
The properties that should remain unchanged must be specifically noted by placing a dollar followed
by that property name. For example, if the text field should not be modified, then the value $text
should be entered in the Output String.
When specifying the output values in the definition column, to use the values of the incoming event
properties, you should specify the exact property name (case sensitive) with a prepended $. For
example to use the event property source, the definition should be $source. If the particular property
has been tokenized and if user intends to use the value of the token, then the format should be
$propertyname$N, where N should be the count of the token starting with 1.
When it is necessary to deliberately have a null value for a specific property of the Output Event,
then the Output String for that property should be left blank.
The default properties of event that can be used in the definition column following $ are: category,
domain, entity, groupName, helpURL, network, node, source, severity, text, WebNMS. Apart from the
listed default properties of the event, user property names can also be used.
For the list of the various Event Properties and their description, refer to Event Properties.
More
Configure additional criteria based on other properties of the event, which could also include the
User properties, apart from the given default set of Event properties.
In the first column of the dialog, specify the “name of the property”, which could be any valid
property of the Event including its user property. While giving the name, ensure that the name has
the same case as given in the event properties. The second column specifies the matching criteria. In
the third column, user can specify the pattern in which the incoming event property has to be
tokenized. The fourth column is for defining the output value of the corresponding property in the
resultant event.
Note: You should note that if a criteria is configured, based on the Event user property and if
no definition is given against that property, then the user property will be dropped in the
resulting Event. The event properties id and time are not configurable using the event
parsers. These fields will be copied to the values as that of the incoming event object.
Note: When user properties are added to events, they can be used in additional event parsers
or custom views.
Add Event
Parser
Add a new Event parser. All the fields in the screen are editable. Ensure the name is unique. If the
entered name matches the existing one, then an error message will pop up with the message “Event
parser of the given name already exists. Should that be replaced?” Clicking “Yes” will overwrite the
existing criteria. Clicking “No” will quit the add operation.
Modify Event
Parser
Modify an existing Event Parser. All fields are editable.
DeleteEvent
Parser
Deletes the selected Event Parser. You can also click on the Event Parser and use the Del Key, or
Control + Del or more than one.
TABLE 9-4 Event Parser Configuration Form (Continued)
Option Description