...
This is a critical concept. The node property will always be the same for any given node. The element property will be somewhat dynamic, usually a regular expression will parse and 'capture' it. The most comment element example would be an interface; gig0/0 versus gig0/1. The stateful property is necessary because the same element may have different events; consider an interface down event versus an OSPF event on the same element (gig0/0).
| Note |
|---|
If any of these three event properties are not set state will not function well. Consider a case where the element property is not set; thus being null. In this case if a 'port down' for gig0/0 was received a 'port up' for gig0/1 would clear the g0/0 'port down' event. Without the element being set opEvents cannot differentiate between interfaces. |
Example parser for the element property.
...
The install version of EventParserRules.nmis has a traplog section that will extract the date, host, trap and details fields for most situations. This article will focus on situations where customers want customization for the remaining fields.
Set the Element
Setting the element is important