m to perform the same job, in fact an event parser converts other types of notifications - such as TL1 messages and user- generated event notifications - into a readable format before filtering events. Event parsers are configured as shown in Figure 12.6. Managing event parsers is the usual operations of adding, modifying, deleting, saving and loading event parsers and re-ordering the sequence of application of the event parsers. Configuring an event parser involves: setting parameters setting match criteria using tokeniser strings defining parameters for the output event object setting up the configured event parser list. The Event Parser Configuration window has several parameters for configuration of an event parser. The first parameter is the "Name" field, which helps identify a parser when managing a list of parsers. The remaining fields of the event parser correspond to event object attributes. 12 Fault Management A AdventNet Event Parser Configuration Configured Event Parsers Field Name Match String Tokenizer String Output String Message $Message Category $Category Domain Network $Source Failure Object $Entity Source Source Severity Unchanged Add Event Parser Modify Event Parser Delete Event Parser Update Close Load From File Save To File Cancel Figure 12.6 Event parser configuration. The output of any event parser is an event object, which is the modified instance of the incoming event based on the definitions configured in the event parser. The match criteria determine whether the event will be parsed by the given event parser or not. Tokeniser strings allow the user to break up the input field into a series of tokens that can then be used in the output event object. If an event is generated by a trap, then the associated trap PDU reference is main- tained in the incoming event object. If the event object contains the trap PDU refer- ence, then the properties of the trap can be used in the event parsers. When an event arrives in the fault management system, the list of event parsers is checked to see whe