Alarms that can be raised against a Unix/Linux connection
- File System Space alarm
- Memory - Physical Memory Available alarm
- Most Active Disk alarm
- Blocked Processes alarm
- CPU Busy alarm
- Monitored Server - Unix/Linux Alarm Action Failure alarm
- Monitored Server - Unix/Linux Alarm Evaluation Failure alarm
- Monitored Server - Unix/Linux Collection Execution Failure alarm
- Monitored Server - Unix/Linux Connection Failure alarm
- Monitored Server - Unix/Linux Planned Outage alarm
- Monitored Server - Unix/Linux Secondary Connection Failure alarm
- Monitored Server - Unix/Linux Unsupported Version alarm
- Network Errors in alarm
- Network Errors out alarm
- Paging in alarm
- Paging out alarm
- Swap Space alarm
- Swapping in alarm
- Swapping out alarm
- Zombie Processes 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.