Alarms that can be raised against a Windows Server connection
- CPU - Average CPU Usage alarm
- CPU - Individual CPU Usage alarm
- CPU - Processor Queue Length alarm
- Disk Queue Length alarm
- Disks - Percentage Used / Free Space alarms
- Disks - Transfer Time alarm
- File - Exceeded Set Size alarm
- Memory - Free System Page Table Entries alarm
- Memory - Percentage Free Virtual Memory alarm
- Memory - Physical Memory Available alarm
- Network - Percentage Bandwidth alarm
- Paging - Disk Activity alarm
- Paging - File Collision alarm
- Services - Service Not Running alarm
- Windows Custom Counters alarm
- Monitored Server - Windows Alarm Action Failure alarm
- Monitored Server - Windows Alarm Evaluation Failure alarm
- Monitored Server - Windows Collection Execution Failure alarm
- Monitored Server - Windows Connection Failure alarm
- Monitored Server - Windows Planned Outage alarm
- Monitored Server - Windows Secondary Connection Failure alarm
- Monitored Server - Windows Unsupported Version alarm
How to acknowledge an alarm
If an alarm is configured to require acknowledgment then each raised instance of the alarm remains present in Spotlight until it is acknowledged.
- Acknowledge alarms in Spotlight Cloud Mobile
- Acknowledge alarms in Spotlight Enterprise
- Alarms FAQ on the Spotlight Cloud web site
How to snooze an alarm
To snooze an alarm is to temporarily remove the visual alert associated with an alarm.
How to configure an alarm
See Configure Alarms to set the thresholds and severities that determine when an alarm is raised. Disable an alarm. Set an alarm to require acknowledgment. Configure keyed alarms. Collect additional diagnostic information on an alarm.
See Configure Alarm Actions to setup actions for Spotlight to take when an alarm is raised. The actions Spotlight can take include running a program and sending an email. Conditions on taking the action can be defined, such as the day of the week, the time of day, the severity of the alarm, the alarm type and the connection type.