Difference between revisions of "UM:Event Processing"

Line 17: Line 17:


== Event Processing Policy ==
== Event Processing Policy ==
Actions taken by event processor for any specific event determined by set of rules called ''Event Processing Policy''. Every rule has two parts – matching part, which determines if rule is appropriate for current event, and action part, which determines actions to be taken for matched events. Matching part consists of four fields:
Actions taken by event processor for any specific event determined by set of rules called ''Event Processing Policy''. Every rule has two parts - matching part, which determines if rule is appropriate for current event, and action part, which determines actions to be taken for matched events. Matching part consists of four fields:


 
{| class="wikitable"
{| class="prettytable"
| ''Source''
| ''Source''
| Event's source node. This field can be set to ''any'', which matches any node, or contain a list of nodes, subnets, or containers. If you specify subnet or container, any node within it will be matched.
| Event's source node. This field can be set to ''any'', which matches any node, or contain a list of nodes, subnets, or containers. If you specify subnet or container, any node within it will be matched.
Line 47: Line 46:




[[Image:]]
[[File:EP_Example1.png||none|alt=Example]]




Line 53: Line 52:




[[Image:]]
[[File:EP_Example2.png||none|alt=Example]]




This rule defines that for events NOKIA_CFG_CHANGED, NOKIA_CFG_SAVED, NOKIA_LOW_DISK_SPACE, and NOKIA_NO_DISK_SPACE, originated from any node, system should generate alarm with text "%m" (which means "use event's message text) and severity equal to event's severity.
This rule defines that for events NOKIA_CFG_CHANGED, NOKIA_CFG_SAVED, NOKIA_LOW_DISK_SPACE, and NOKIA_NO_DISK_SPACE, originated from any node, system should generate alarm with text "%m" (which means "use event's message text) and severity equal to event's severity.


== Alarms ==
== Alarms ==
AutoPatrol
191

edits