Event Management
Overview
Events do not require a direct report from a user. They are automatically generated by the monitoring system and represent status messages about a system's state. The term "event" can be understood as a trigger or incoming notification that is categorised by relevance.
Software support enables filtering and can be configured so that exception messages are forwarded to the responsible parties as quickly as possible.
Event Types
Information
A status message about a system without any action required.
The system is operating normally; no intervention is needed.
Example: Network utilisation is between 45 % and 48 %.
Warning
A status message indicating the need for closer monitoring; action may be required soon. The warning signals that a problem is approaching.
Example: The RAID data array reports a remaining capacity of 20 %.
Exception
A status message requiring immediate action. The system or service has failed or exceeded a critical threshold. Exceptions typically lead to an Incident.
Example: The 48-port network switch has failed.
Event Classification Examples
| Event | Type | Reason |
|---|---|---|
| Hard drive capacity at 80 % | Warning | Not a problem yet, but could become one soon |
| Network running stably at 40 % load | Information | Normal system state |
| Web-based ERP system unreachable | Exception | Outage requiring immediate action |
| Web server running stably at 85 % load | Warning | High load, approaching critical |
| 48 of 50 User CAL licences in use | Warning | Licence limit almost reached; becomes an exception if exceeded |
| 52 devices connected but only 50 Device CAL licences available | Exception | Licence limit exceeded |