Turning Off Performance Data Output | Monitoring NetApp - Jan 3, 2015
[…] a check for each volume that outputs performance data and the corresponding graph. Thanks to the collector architecture no additional requests have to be sent to the […]
#### [Collectors and Distributed Monitoring | Monitoring NetApp](https://blog.monitoring-plugins.pro/posts/collectors-and-distributed-monitoring/ "") - Jan 4, 2015 […] Collectors have some great advantages: the monitored device is put under less computational load and a greater flexibility for the configuration of service checks.
Our present monitoring-plugin for NetApp FAS devices, named check_netapp_pro is based on the so-called collector architecture. This allows us to monitor even the most complex storage-systems like Fabric Metro Clusters.
The collector architecture works as follows:
Collectors are distinct scripts that collect all the data that the checks require and saves it in a Store on the Nagios Server. The checks have access to the Store and no longer contact the NetApp devices themselves.
Version 3.0.7 of our Monitoring Plugins for NetApp (check_netapp_pro) will be available soon and will include a number of new features that have been implemented based on feedback we received from our customers:
New Check PerfSys: Not entirely new, but taken over from the stable version 2.x to version 3.x. In this new release, system-wide performance counters such as transfer-rate or _operations per second _ can also be checked on cluster mode Filers.
check_netapp_pro: What’s New in Version 3.0.7 | Monitoring NetApp - Aug 1, 2014
[…] ← Mammamia! Check the number of Snapshots per Volume → May 31, 2014 Nagios Plugins for NetApp, NetApp, NetApp Monitoring, Operations per Second, Performance, Transfer Rate, Uncategorized cDot, Cluster Mode, Monitoring Plugin, NetApp, Operations per Second, Performance Monitoring, transfer-rate Leave a comment […]
#### [Quality Assurance through Mammamia Reports | Monitoring NetApp](https://blog.monitoring-plugins.pro/posts/quality-assurance-through-mammamia-reports/ "") - Oct 2, 2014 […] receiving the first ‑‑mammamia reports from our customers, we can already see how they affect the quality of our checks.
To facilitate communication between users and developers, we are introducing a new switch: --mammamia The idea behind this switch: advanced users that want to test a script or a function which appears not to be working properly usually switch to the command line. Should they require the assistance of the developer, they previously had to include the output of the script in an email. In most cases, this was not enough and resulted in more requests from the developer such as: creating and sending rawdump, creating and sending verbose output – annoying!
The new version of **PerfVolume **is now able to handle any amount of volumes on a filer. The formerly common error message “Not enough memory to get instances” is a thing of the past. Should the amount of instances exceed the maximum possible value, the plugin would start a second call at runtime in order to collect the missing instances. The core task of the PerfVolume check has remained the same: continuous monitoring of latency (per volume latency) on NetApp filers.
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 nutshell, during such a check, it can happen that a critical service check in Nagios gets acknowledged (Service Acknowledgement) because of a specific volume.
Half a year ago there was very little demand for Nagios plugins that support Cluster Mode. Recently, we have received more and more requests for just such plugins. We are looking at Q4 2013 to launch our new release of Nagios Plugins for NetApp, Version 3.0, with added support for cluster mode.