No Instances can be OK
For obvious reasons, the first checks that we developed primarily monitored volumes and aggregates. The overall method took the approach of sending an UNKOWN alarm if no volumes or aggregates ...
Instances
No instances should be ok?!
The --no_instances=OK switch has been available for some time now. It prevents for example a LUN check that can’t find any LUNs with a not always matching UNKNOWN not to seek any unneeded ...
No instances can be OK now!
As of release 3.5.0 it will be possible to configure checks so that the non-existence of instances does not trigger an alarm. The default configuration won’t change, meaning that an UNKNOWN will ...
Checking a specific Nodes Instances
Since 4.0.0 every over-all check has a feature, which we call “instance-name contains node-name”. We have introduced this as an replacement for the sporadic available --node|--vserver parameter ...