ed. This may or may not be used, depending on the application. Node: Enables using a node value for the event. This may or may not be used, depending on the application. Source: Typically the source name for a given event. Group Name: Helps to group meaningful events - and hence alerts - in a mean- ingful way. Help URL: The URL that refers to the file which provides detailed help for a given event. While specifying values that are output to the event object generated, the user can use the information in the incoming trap PDU. The information in the trap PDU is accessed using tokens which represent the values of the trap fields. Incoming traps are parsed by configuring a list of trap parsers. Only one trap parser can be applied to a given trap. The match criteria in the parser determine whether or not a specific trap matches the trap parser. 12.12.2 Events To identify the failure object corresponding to an event, traps and input events should be parsed and necessary details given. This parsing is useful in defining other fields of the event or alert. FMS allows detailed parsing of the input events by event parsers. FMS allows dynamic configuration of event parsers from the fault management client. This can be done from the event browser of the fault client through the event parser configuration screen (see Figure 12.29). The event parser configuration window has several parameters that help in con- figuring an event parser. The first parameter 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. The output of any event parser is an event object, which will be the mod- ified instance of the incoming event based on the definitions configured in the event parser. If any field is empty in the definition column, then that particular property of the outgoing event will be an empty string. Additional criteria can be configured OSS for Telecom Networks Event P