Reference Guide

8
Command | Monitor alerting
Local alerting involves displaying user messages and writing to the Windows event log. Remote alerting is
accomplished through WMI indications. When Command | Monitor detects an event, it generates an
alert, which can be transmitted through the WMI service to a remote management application that is
subscribed to that alert type.
When an alert is generated, Command | Monitor supports four types of notification:
• NT event log
• WMI event
• SNMP traps
In Command | Monitor, each type of event (for example, CurrentProbe, TemperatureProbe, Smart, and so
on) that gets logged is provided with an unique event ID number. The events have unique IDs to allow log
scraping; this way you can programmatically look at the event log and determine what Command |
Monitor events have occurred.
You are also provided with an option to receive either a single alert or a limited number of alerts of the
occurrence of an event, of a given type. You can mask out specific events and can generate single alert
messages for only those events.
Command | Monitor recognizes the following eight WMI severity levels (represented by integers 0
through 7):
• UNKNOWN = 0
• OTHER = 1
• INFORMATION = 2
• WARNING_DEGRADED = 3
• MINOR = 4
• MAJOR = 5
• CRITICAL = 6
• FATAL_NONRECOVERABLE = 7
NOTE: Events with CRITICAL severity will cause Command | Monitor to shut down the local system
after a 60-second delay.
The lowest WMI severity level that Command | Monitor sends is WARNING_DEGRADED and the highest is
CRITICAL. The severities of Command | Monitor events are listed in Table 2-1. Command | Monitor sends
local alerting and remote alerting for all the listed events.
344