ther the incoming event satisfies the match criteria of the event parser. If an event parser does match, then the event is passed through that parser. The outgoing event from the parser is then matched with the remaining parsers (if any) in sequence. This process continues until the parsed event matches no more parsers. A set of parsers might be available in the event parsers list. Among these, a user can select a parser and disable it. When an event is raised, certain actions may be executed aside from parsing. Event filters can perform automatic actions when an event occurs, such as sending an e-mail, suppressing the event and generating traps. Custom classes can also be executed upon generation of an event. OSS for Telecom Networks AdventNet Event Filter Configuration Configured Filter List Event Filter Actions Configured Action Action Type Suppress Action Run Action Send Trap Action E-Mail Custom Filter Filter Action Details Filter Name New Match Criteria Severity Message Click To Edit Category Domain Network Entity Source Event Filter Filter Action Update Filter Load From File Close Modify Delete Modify Delete Cancel Filter Save To File Figure 12.7 Event filter configuration. Figure 12.7 shows the event filter configuration screen. There are many ways in which events can be filtered. Filter parameters include: Filter name. Severity. Message: Message is matched with the message of the incoming event such as interface failure, status poll failed. Category: Category to which the event belongs. Domain: Domain-specific information, which might be based upon physical location, functional or logical categorization of the source of the event. Network: Network to which the source of the event belongs. Source: Source of the event. Node: Additional information about the source of the event. Entity: Exact device in which the problem has occurred. These parameters can be used to configure match criteria which determine whether or not an incoming event should be filtered. 12.8.3 Event API Event-handling APIs enable indepe