In order to monitor the configuration-health of Metro-Cluster Servers we are introducing a new check: MetroClusterVserver , monitoring all or specific Vservers. The check can be configured to monitor the Vservers of a specific node and/or those fitting a specific naming pattern. Furthermore, the switch --skip_reason can be used to configure reasons that won’t set off an alarm.
Related Posts
- Monitoring Cluster Peer Health Jan 8, 2016
- Unassigned Disks in DiskPaths Apr 26, 2016
- No instances can be OK now! Mar 31, 2016
- -timeout Bug Mar 8, 2016
- DiskCount counts SSD spare disks Mar 8, 2016
Comments