|
|
In order to identify the failure object corresponding to an Event, the traps and the input Events should be parsed and the necessary details should be given. Trap parser does the job of making the notifications readable to the user. Event parser refines the message conveyed by the Events. Though both the Trap parser and Event parser seem to perform the same job, the need for an Event parser before filtering of Events is to convert the other types of Events like Threshold Events, Status Poll Events etc. into a readable format.
The Event Parsers can be configured using the Event Parsers Configuration tool which can be invoked in the following ways:
Using the script
Executing the file EventParserConfig.sh/bat
Using the Web NMS Launcher
Administrator Tools -->Event Parser
This will open up the Event Parser configuration screen, which will look like the one given below:
You can parse the Events by filling in the following parameters. The first parameter in the Event Parser window is the "Name" field to help identify the parser distinctly, when managing a list of parsers. The remaining fields of the Event Parser can be viewed as a table, where the rows correspond to the event object attributes. There are three columns in the table to be configured for the event parser.
Setting the Match Criteria - The first column Match String corresponds to the match criteria, that determine whether a particular Event should be parsed by the Event Parser or not.
Tokenizer Strings - The second column fields allow tokenizing of the input Event by a set of tokenizer strings. This will allow for detailed parsing of the Event.
Definition for output Event Object - The third column i.e., Output String fields are used to set the definition for the output Event object of the Event Parser.
For more details regarding the above mentioned fields, please refer to Configuring Event Parsers.
Options available with Event Parser Configuration
Various options that are available with the Event parser configuration are:
Add Event Parser
Modify Event Parser
Delete Event Parser
Save To File
Load From File
Re-ordering Configured Event Parsers
To save the changes to the Event Parser, use the Save To File option.
Dynamic configuration using API
You can also configure the Event Parsers dynamically using the EventAPI. The methods
setEventParser (java.util.properties.prop)
can be used to set an Event Parser in the server. Please refer to javadocs
for com.adventnet.nms.eventdb.EventParserAPI
for more details
on the API methods.
Dynamic Configuration from Web NMS Client
Web NMS allows dynamic configuration of Event parsers from Web NMS Client. This can be done from the Event browser of the Web NMS client. For more details refer to Configuring Event Parsers.
Enable or Disable Event Parsers
Among the set of parsers available in the Event Parsers list, you can select a Parser and make it dormant or inactive. By disabling the parser, the actions specified under the event parser will not take place when an event with the specified match criteria passes the parser.
You can enable or disable the Event parsers using the "enable" parameter of event.parsers file present in <Web NMS Home>/conf directory.
Possible values for the 'enable' parameter
true - the corresponding filter will be enabled
false - the corresponding filter will be disabled
Default value - true
An example entry in the event.parsers file will be similar to the one shown below:
<EVENT_PARSERS>
<PARSER
name="Test parser"
severityDefn="Unchanged"
nodeMatch="$Source"
enable="true" />
</EVENT_PARSERS>
|
|