The OS Cluster Layer
This layer will appear only if the ‘Fail over cluster service’ is enabled on the Windows system/server being monitored. With the help of the tests mapped to this layer, you can determine the following:
- Know the clusters that are currently managed by the Windows Failover Cluster Manager;
- Know which nodes are part of a cluster;
- Determine the current state of each node;
- Rapidly detect the failure of the cluster service on the monitored node;
- Identify the services/applications that have been clustered, promptly detect service/application failures, and pinpoint the probable reasons for the same;
- Identify cluster networks that are currently down;
- Pinpoint cluster resources that are offline;
- Track the current capacity and usage of cluster disks and cluster shared volumes and proactively detect potential space crunches.
Figure 1 : The tests mapped to the OS Cluster layer
The tests mapped to the OS Cluster layer run only in the agent-based mode. This is why, you need to install an eG agent on at least one node in the cluster to enable these tests to report cluster-level metrics. For best results however, it is recommended that you install an eG agent on each node in the cluster; this way, even if one node goes down due to any reason, cluster health can continue to be monitored using the agents on the other nodes.