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 still be sent when the performance getter (performance collectors) don’t find volumes, disks, luns, etc… …
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 attention. Recently, we received an increasing number of requests that express the desire for such a switch for collectors …
Snapshots can be used not only to monitor volume usage by snapshots, but also the number of snapshots that meet a certain criteria, e.g snapshots that exceed or fall bellow a certain age or have a specific name.
Finding outdated snapshots In order to receive alarms for orphaned and outdated snapshots, one would use the …
Today we are introducing a new switch for all checks: ‑‑alarm_limit=0|1|2 When would we need this new switch? It will most probably be used for Raidstatus or SnapMirrorState , every time when an administrator thinks that an alarm marked as CRITICAL is too far fetched and WARNING would be enough. An example: $ …
The abbreviation rm_ack stands for remove service acknowledgement, which refers to a rather simple algorithm that can be used to identify masked alarms. Masked alarms are a phenomenon that solely appears with checks on multiple instances, such as the simultaneous checking of all volumes on a NetApp device. In a …