AutoPatrol
191
edits
Difference between revisions of "UM:Event Processing"
m
→Alarms Overview
| Line 61: | Line 61: | ||
As a result of event processing some events can be shown up as ''alarms''. Usually alarm represents something that needs attention of network administrators or network control center operators, for example low free disk space on a server. Every alarm has the following attributes: | As a result of event processing some events can be shown up as ''alarms''. Usually alarm represents something that needs attention of network administrators or network control center operators, for example low free disk space on a server. Every alarm has the following attributes: | ||
{| class="wikitable" | |||
{| class=" | |||
| Creation time | | Creation time | ||
| Time when alarm was created. | | Time when alarm was created. | ||
| Line 89: | Line 87: | ||
|} | |} | ||
| Line 100: | Line 95: | ||
|- | |- | ||
| Severity | | Severity | ||
| Alarm's severity | | Alarm's severity - Normal, Warning, Minor, Major, or Critical. | ||
|- | |- | ||
| Line 111: | Line 106: | ||
|} | |} | ||
=== Generating Alarms === | === Generating Alarms === | ||
To generate alarms from events, you should edit "Alarm" field in appropriate rule of Event Processing Policy. Alarm configuration dialog will look like this: | To generate alarms from events, you should edit "Alarm" field in appropriate rule of Event Processing Policy. Alarm configuration dialog will look like this: | ||