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…
All articles in English
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…
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…
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…
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…
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…
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…
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…
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…
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…
We have one report, that changing the setup from a chain setup (netapp01 → netapp02 → netapp03) to a star setup (netapp01 → netapp02 ➕ netapp01 → netapp03) makes stoping some collectors (e.g. get_netapp_cm.pl) with an error…