Blocked Processes alarm

Processes can become blocked when they are waiting for: disk I/O completion, network I/O completion, or a shared resource. A high level of blocked processes may indicate an under-configured machine.

CPU Usage alarm

Raised when the total CPU utilization of the system exceeds a threshold. The CPU may encounter a large number of requests, or there may be un-tuned SQL, which uses excessive amounts of CPU.

File System Space alarm

Raised to indicate that the file system is full or filling up. If the file system fills up completely, no more data can be written to it.

Memory - Physical Memory Available alarm

Raised when the available memory is insufficient. It indicates a potential memory leak in running software, or a shortage of required memory.

Monitored Server - Unix/Linux Alarm Action Failure alarm

Raised when a configured Alarm Action failed to evaluate.

Monitored Server - Unix/Linux Alarm Evaluation Failure alarm

Raised when Spotlight Cloud failed to evaluate a given alarm from a given collection.

Monitored Server - Unix/Linux Collection Execution Failure alarm

Raised when a given collection failed to execute against the monitored server.

Monitored Server - Unix/Linux Connection Failure alarm

Raised when Spotlight Cloud fails to connect to the Unix/Linux Server.

Monitored Server - Unix/Linux Planned Outage alarm

Raised during a planned outage of the connection, and cleared upon its completion.

Monitored Server - Unix/Linux Secondary Connection Failure alarm

Raised when the Unix/Linux Server is not responding.

Monitored Server - Unix/Linux Unsupported Version alarm

Raised when the monitored version or flavor of Unix/Linux is not supported by Spotlight Cloud. Some collections may fail because Spotlight Cloud has not been tested against this Unix version or flavor yet.

Most Active Disk alarm

Raised when the read/write rate of the most active disk exceeds the configured threshold.

Network Errors In alarm

Raised when the number of erroneous network packets coming into the monitored Unix/Linux connection per second exceeds the predefined threshold. This alarm may warrant investigation as even a low error rate can indicate network problems.

Network Errors Out alarm

Raised when the number of erroneous network packets sent by the monitored Unix/Linux connection per second exceeds the predefined threshold. This alarm may warrant investigation as even a low error rate can indicate network problems.

Paging In alarm

Raised when the memory of the monitored Unix/Linux connection is demonstrating an abnormal page in rate. A large number of page ins may be a symptom of a large number of recent page outs.

Paging Out alarm

Raised when the memory of the monitored Unix/Linux connection is demonstrating an abnormal page out rate. If an active process asks the kernel for more memory than there is immediately available, the kernel will write old memory pages out to swap space. This is known as paging. To stop paging, make sure that there is enough RAM available to support the size of the processes you want to run.

Swapping In alarm

Raised when the number of processes swapped from disk per second exceeds the predefined thresholds. A machine that is swapping processes to or from disk is usually under-configured for its workload.

Swapping Out alarm

Swapping out represents the number of processes swapped to disk per second. A machine that is swapping processes to or from disk is usually under-configured for its workload.

Swap Space alarm

Raised when the total amount of swap space allocated to a Unix/Linux host is almost full. Running out of swap space may indicate a runaway process or an under-configured machine.

Zombie Processes alarm

Raised when the number of zombie processes exceeds the configured threshold. A high level of zombie processes is indicative of the presence of an inferior program, or an entry in /etc/inittab (or equivalent) preventing init from completing its startup sequence.