It’s all too easy to assume that everyone else knows what you know. We tend to take it for granted that all technical users are familiar with regexes. And also that, being familiar, we assume they also know how to use them to best advantage. This is not always the case, as a recent support call made clear. The …
Obviously, one of the first plugins that we implemented was designed to monitor volumes and aggregates and their respective usage (“how many bytes are still available”). This plugin is called Usage and from the get-go it could monitor disk space usage in bytes as well as the number available (or used) …
The switch ‑‑svm_in_name for the usage check was first introduced in version 3.9.1. We would like to take a look at an intersting use case for this new switch. ‑‑exclude|‑X and ‑‑include|‑I can be used to filter the list of instances by name. If the instance name starts with the name of the Vserver separated by a dot, …
When monitoring volumes with very different sizes using usage it might be desirable to have the option to configure different thresholds independently of the size of the volumes. The easiest way of doing this would be to set different percentages for small, medium and large volumes. Example Lets say… …
After having received feedback from a client saying the cluster mode collector get_netapp-cm.pl needs up to 45 seconds or more to collect 4500 snapshots, we looked into possibilities to accelerate the getter. In previous versions we relied on the default setting of the NetApp API which is set to 20 instances to be …
3.4.1_01 FIXES USAGE/SHELF-ENVIRONMENT, DISKCOUNT, WORKLOAD, LUNSIZE Released 2016-03-18
Fixed Usage-Check: Handling of volumes with no state-attribute shelf-environment-object in cm-getter needs a node-name (sometimes) New and improved new DiskCount check (counts spare-disks per type or storage-pool) new …
_Unknown _volumes are currently not supported by the Usage plugin included in version 3.4.0. As a workaround we recommend excluding the respective volumes via the X switch after having verified their unknown state using -explore. As of the next release (3.4.1) the plugin will skip unknown volumes (and outputs the …
With Usage it was always mandatory to set the ‑‑vserver|‑‑node|‑s argument. This means it necessary to specify for which node or vserver the volumes should be monitored. The argument expects either the node or vserver name, depending on the device being monitored. This has caused quite some confusion in the past. In …
DataONTAP 7.x will no longer be supported by check_netapp_pro. Nevertheless, some checks might still work relatively well. For example, the aggregate usage can be monitored with the check Usage, if the Server/Node name is set to the host name (--vserver|--node|-s). Here an example: $ ./get_netapp_7m.pl -H 10.25.0.22 -o …