New checks and products have been released. The most important are Check NetApp-REST v1.1.0 which adds two new checks and the --config-Option. See also Check NetApp-REST Release History. Check E-Series v0.0.1-rc.1 has a health-check (check_eseries_health) to monitor the health-status of NetApp E-Series Storage running the SANtricity OS. More details are in the Check E-Series documentation.     ..read more

After heavy testing both internaly and on the distributors site we finally can release the brand new 1.0.0 version of Check NetApp-REST. Check NetApp-REST is a supplemental product to our proven suite of Perl checks (now called Check NetApp-ZAPI) aimed to be both future prove and easy to install. It’s main advantages are: easy install: Binary-only, precompiled checks with no dependencies. Motto: copy & run. future prove: Use the latest official NetApp API (RESTful API, only available on Ontap >=9.6) Download and Documentation Customers of Check NetAppPRO can download both the checks a ..read more

We have discovered an issue in the new 6.x versions of check_netapp_pro if a getter contacts the new RESTful API of NetApp. These getters require an explicit --stm (e.g. --stm=1h). Otherwise the collected storefiles are not deleted and could fill up the monitoring servers disk. Again this does affect installations only if both of the following conditions are met: the plugins version is 6.x  the plugins getter contacts the RESTful API of the filer (Ontap 9.6/9.7) In the next version of the plugins we will set a reasonable default.  ..read more

We have at least one confirmed report, that our latest release v6.0.0 has performance problems in large environments when running many checks at the same time. There seems to be a limit of approximately 12 checks per second due to the overhead of running a docker container. We are working on a solution and will report here once we can provide an updated version. Customers with large environments may wait with an upgrade to the v6.0.0 if they expect to run into the above mentioned limit. We are sorry for the problems this may have caused . Please do not hesitate to contact us if you need f ..read more

After extensive testing we released the next major version 6.0.0 today. As already announced this version brings: Easy installation and update without dependencies on Perl or Perl-Modules.  Getter amd checks compatible with NetApps new RESTful API New checks and options More details are in the release history. This version is already available on your distributors portal. The completely rewritten and new documentation is available online at docs.monitoring-plugins.pro ..read more

We just pushed the first RC for the upcoming 6.0.0 version to the Distributors Portal. Customers who would like to test are very much appreciated! (Pls. check with the distributor to get access to unstable releases as well, if you do not see them on your account.)  The 6.0.0 version brings a completely dockered and therefore dependency free installation plus new checks and options. Please read the release history for details ..read more

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 (not available any more).  So since then each instance-name has the name of its node prefixed. This allows to use the --include|--exclude parameters to filter for all instances of a specific node. E.g. if you have a new-node with a different hardware you may want to check only the ports of this new-node: ./check_netapp_pro.pl NetPort -H filer --include="^new-node\." The above example would do exact ..read more

We are constantly trying new methods of installing the plugins so to make installation and upgrade easy and scriptable (rpm, …). We found the Perl dependencies being the main obstacle and finally favorite a solution depending on docker. So in the future you could get a fully installed docker image with anything inside and ready to run. This image will of course require docker to run on your monitoring server. But in turn you won’t need to have Perl or any of its plugins installed. If this sounds either interesting or impossible or something in between to you – we would be very thankful fo ..read more

The 5.3.0 version, released yesterday includes a new check to monitor the EMS(Event Management System)-Logfile. This allows several new checks among them one to send an alarm, if an unusal high number of autogrow-events take place. Let’s have some examples:   # check myfiler for autoSize events and alarm according to the defaults check_netapp_ems -H myfiler --name=wafl.vol.autoSize.done # same as above, but check only on node 01 check_netapp_ems -H myfiler --node=myfiler-01 --name=wafl.vol.autoSize.done # check any autoSize events (even the failed ones) check_netapp_ems -H myfiler --name ..read more

Our quite new SnapCenter check can filter for resource-groups and policies. Until now one had to precisely define which resource-groups should get checked. In some situations the resource-group name changes. To allow checking such resource-groups without having to constantly change the filters in the service-check configuration we are introducing regexmatching for these filters. Example Let me show you an example: If a resource-group sometimes changes from … AT01_HA_D01   to   AT01_HA_D01_SR (and vice versa), … you can check both resource-group with the same service-check by setting: --resour ..read more