AutoPatrol
191
edits
Difference between revisions of "UM:Event Processing"
→Event Processing Policy
| 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. | Actions taken by event processor for any specific event determined by set of rules called ''Event Processing Policy''. | ||
[[File:Event_Processing_Policy.png|frame||left|Event Processing Policy Screen]]<br style="clear: both" /> | |||
Every rule has two parts - a matching part (called '''Condition''' in the rule configuration dialog), which determines if the rule is appropriate for the current event, and an action part, which determines actions to be taken for matched events. A matching part consists of four fields: | |||
{| class="wikitable" style="width: 70%" | {| class="wikitable" style="width: 70%" | ||
! Attribute || Description | ! Attribute || Description | ||
|- | |- | ||
| ''Source'' | | ''Source Objects'' | ||
| | | One or more event's source objects. This list can be left empty, which matches any node, or contain nodes, subnets, or containers. If you specify subnet or container, any node within it will be matched. | ||
|- | |- | ||
| '' | | ''Events'' | ||
| Event code. This field can be | | Event code. This field can be left empty, which matches any event, or list of event codes. | ||
|- | |- | ||
| ''Severity'' | | ''Severity Filter'' | ||
| Event's severity. This field contains selection of event severities to be matched. | | Event's severity. This field contains selection of event severities to be matched. | ||
|- | |- | ||
| ''Script'' | | ''Filtering Script'' | ||
| Optional matching script written in NXSL. If this field is empty, no additional checks performed. Otherwise, event will be considered as matched only if script | | Optional matching script written in NXSL. If this field is empty, no additional checks performed. Otherwise, the event will be considered as matched only if the script returns non-zero (TRUE) return code. For more information about NetXMS scripting language please refer to the chapter [[UM:NetXMS_Scripting_Language_(NXSL)|NetXMS Scripting Language (NXSL)]] in this manual. | ||
|} | |} | ||
| Line 47: | Line 51: | ||
Examples: | Examples: | ||
[[File:EP_Rule_Config_example_1.png|frame||left|Rule Configuration Example 1]]<br style="clear: both" /> | |||
This rule defines that for every major or critical event originated from a node named "IPSO" two e-mail actions must be executed. | |||
This rule defines that for every major or critical event originated from | |||
[[File:EP_Example2.png||none|alt=Example]] | [[File:EP_Example2.png||none|alt=Example]] | ||