The newest unstable release 3.9.2_04 is now available in the Q-portal. It includes the following changes:
–check_only=without_lun for the SnapshotlessVolume check Further fix for check_netapp7_vfiler
Wit the next release, SnapshotLessVolumes will receive the option ‑‑check_only=with_lun|without_lun. 7m filers can also use without_lun_7m. With this option you can limit the check to volumes with or without LUNs, regardless of any naming conventions.
In June 2017 OvercommitAggr received an essential new feature: the new metric growth. Using --metric=growth one can calculate the usage of a thin-provisioned aggregate for a specific period in the future based on the current trend. Unfortunately this feature was not well documented and the usage of the different …
Our newest unstable release 3.9.2_02 is now available and includes the following changes:
New check LunAlignment New check PerfSysNode For more information head to our release history .
Shortly we will be releasing our new check LunAlignment . This checks searches for misaligned LUNs per Vserver and issues a warning when a specific threshold has been exceeded. If you would like to test this check before release, please us send a quick message to il@netapp-monitoring.info .
We are adding a new counter to PerfDisk :``` -—————————————————————————– total_transfers Total number of disk operations involving data transfer initiated per …
With the next release (3.9.2) PerfVolume will be able to monitor several NFS counters.
Performance Counter on a Qtree level? Additionally, we are thinking of retrieving counters on a Qtree level. This would require a new check PerfQtree.We appreciate your feedback, please contact us directly.
Starting with the next release (3.9.2) the head check will display additional information next to the name of the node, such as the model, serial number, DataONTAP version as well as the uptime in days. This way one can see these details directly in the monitoring system without having to connect via ssh. Example:``` $ …
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, …
Because of a bug related to service processors (1) we are currently developing a new check that will monitor the status of service processors. We are aiming to include this check in version 3.9.2 (planned to be released in Oktober 2017). Specification for the ServiceProcessor check We will gladly provide our customers …