Check NetApp-REST on blog.monitoring-plugins.pro

check_netapp as a Single Binary

Wed, 05 Aug 2026 00:00:00 +0000

As of v4.0.0-beta.3, Check NetApp-REST ships a new binary called check_netapp. It bundles all 20 ONTAP-REST checks — volume, aggregate, snapmirror, disk and so on — as subcommands of a single executable, in addition to the familiar individual check_netapp_* binaries.

Why a single binary?

Each check_netapp_* binary is a statically linked Go executable of around 10 MiB. With 20 of them in the package, that adds up to roughly 200 MiB on disk — for what is, under the hood, largely the same runtime and shared library code repeated 20 times.

Strengthening the Software Supply Chain: Signed Releases and SBOM Scanning

Tue, 19 May 2026 00:00:00 +0000

We’ve shipped two security improvements that make it easier to trust the plugins you download and run from us. Both are now live and will apply to all future releases.

Signed Release Archives

Every release archive on https://releases.monitoring-plugins.pro/ now ships with a detached OpenPGP signature — a small .asc file next to each .tar.gz. Publishing an archive without a matching signature is no longer possible, and we have retroactively signed every archive that was already available, so the complete release history is covered.

Direct Distribution of NetApp Monitoring Plugins

Tue, 02 Sep 2025 00:00:00 +0000

As of October 1, 2025, Activaria has taken over the distribution of the NetApp Monitoring Plugins. Previously distributed by Quorum Distribution GmbH, the plugins will now be provided directly by us as the original developer and manufacturer. Existing contracts, including active subscriptions remain fully in effect and will be serviced by Activaria. To ensure continued delivery, the necessary customer information has been securely transferred to us.

The latest software releases are always available for download at https://releases.monitoring-plugins.pro/ using your existing contract number.

Possible false negative: Broken disks have no node

Sat, 02 Aug 2025 00:00:00 +0000

The following text discusses the possibility of a false negative result, depending on your configuration. Please read it carefully.

Recently we got an interesting bug-report: A broken disk did not get alarmed by the check_netapp_disk container-type-plugin. This false negative happened because of a configuration, where disks are checked per node:

check_netapp_disk container-type -H filer … ‑‑include=~^NODE-B\.

This will check all disks on NODE-B. But a broken disk may not be related to any node and so it wont show up in the results.

Check NetApp REST v3.2.0 released

Tue, 20 May 2025 00:00:00 +0000

New Check for Disk Stats (iops, throughput) in v3.2.0

New Check: check_netapp_disk stats to monitor disk-path-quality (failed iops), throughput and other disk-metrics.
New switch --no-include-exclude-message: Do not show the message with the count of included/excluded instances.

For further details please read the release notes and the documentation .

Lots of new checks in v3.1.0 (stable) and v3.2.0-beta.3

Tue, 11 Mar 2025 00:00:00 +0000

New Checks in v3.1.0

check_netapp_node service-processor has got new subcommands to check the service-processor
- state (online/offline)
- last-update-state (passed/failed)
- is-ip-configured
- link-status
The firmware version is now printed into the message.
check_netapp_lun state : Checks if luns are online/offline and their mapping state.

New Check in v3.2.0-beta.3

check_netapp_disk stats monitors the disk-path-quality (failed IO-operations), througput and other disk-metrics.

For further details please read the release notes and the documentation .

v3.0.0 Released: Checks for Node-Hardware, Flexcache, Volume-State, Inodes in Aggregates and Volumes

Mon, 22 Jul 2024 00:00:00 +0000

❗️Check NetApp-REST introduces a breaking change beginning with v3.0.0.

New Checks

Beside of the above mentioned UI-change we offer a lot of new checks:

Node: fan, power-supply, temperature, NVRAm battery, node state (up/down), ha state, give-back state
Check for the the flexcache connection status
Volume: State- and autosize checks
Inode (max-files) checks for both volumes and aggregates
Aggregate-state check (online, offline)
LIF check (administrative-status, operational-status, is-home)

For further details please read the release notes and the documentation .

New String & Regex Values

Wed, 21 Feb 2024 00:00:00 +0000

Check NetApp-REST introduces a breaking change beginning with v3.0.0.

Change

For parameters that previously expected a regular expression: Beginning with the v3.0.0 release, values which do not start with a tilde (~) are interpreted as strings that must match exactly, and not as regex patterns.

Motivation

The new notation is more intuitive, as the former could lead to false negatives, as shown in this example:
The option ‑‑exclude=vol1 also excluded vol10 or vol11 or even somevol123. Now, with the new notation, it does exactly what you would expect at first glance: it only excludes vol1.

Check NetApp-ZAPI will not be able to monitor next year's ONTAPI releases

Mon, 28 Nov 2022 00:00:00 +0000

NetApp’s ZAPI interface (now called ONTAPI) will reach end of availability (EOA) in January 2023. Therefore the checks from Check NetApp-ZAPI won’t be of much use in the near future. Fortunately all customers for Check NetAppPRO can use the future-proof Check NetApp-REST with the same license and therefore without additional costs.

ZAPI EOA: Timeline and Recommendations

NetApp announced that ONTAP release in FY22-Q4, will be the final ONTAP version to include ONTAPI (former called ZAPI).

RESTful Spare-Disk and -Partion Check

Thu, 27 Oct 2022 00:00:00 +0000

The RESTful Spare-Disk Check has got subcommands for checking both spare-disks and spare-partions.

Example for checking spare-disks

./check_netapp_spare disk -H filer
NETAPP_PRO SPARE OK - 28 disks checked
...

Checks all nodes for sufficient spare-disks.

Example for checking spare-partitions

./check_netapp_spare partition -H filer
NETAPP SPARE WARNING - 68 partitions checked, 68 WARNING
prod-na-01.1.0.23.P3: 1 spare-disks (WARNING)
prod-na-01.1.0.23.P2: 1 spare-disks (WARNING)
prod-na-02.1.0.23.P1: 1 spare-disks (WARNING)
...

Checks all nodes for sufficient spare-partitions.

About the Check NetApp-REST plugins

The monitoring plugins check_netapp_* for Nagios®-compatible monitoring frameworks like Nagios Core, Nagios XI, op5-monitor, Icinga, Shinken or Zabbix are enhanced check programs for NetApp filers.

Searching the blog

Wed, 16 Mar 2022 00:00:00 +0000

Over the years, this blog has accumulated almost 300 articles. Unfortunately, the built-in JS-based search is overwhelmed by this. We have therefore switched the search bar at the top to an external search engine called MetaGer.

Why MetaGer?

MetaGer is a search engine supported by the non-profit SUMA-EV, Association for Free Access to Knowledge. MetaGer protects against censorship by combining results from many search engines. The source code is free and open source and respects your privacy.

New Check: Storage Port Status (degraded)

Thu, 27 Jan 2022 00:00:00 +0000

We have got this request:

Recently we have noticed that some of our fiber optic cables have degraded, this is sadly not reported anywhere else exept with the commands below…
STOR04-A1::*> storage port show -node STOR04-A1-01
 
                             Speed
Node               Port Type (Gb/s) State    Status
------------------ ---- ---- ------ -------- ---------------
STOR04-A1-01
                   0a   SAS       6 enabled  online
                   0b   SAS       0 enabled  offline
                   0c   SAS       6 enabled  online-degraded
                   0d   SAS       0 enabled  offline
                   3a   SAS       0 enabled  offline
                   3b   SAS       6 enabled  online
                   3c   SAS       0 enabled  offline
                   3d   SAS       6 enabled  online
                   6a   SAS      12 enabled  online
                   6b   SAS      12 enabled  online
                   6c   SAS      12 enabled  online
                   6d   SAS      12 enabled  online
12 entries were displayed.
 
The cable in question is a QSFP copper to optical LC and is used because the disk shelfs are located in another server room. As you can see from the details above it is degraded, and this is most likely because of dust on the connectors.

RESTful Volume Snapshot Check

Mon, 13 Dec 2021 00:00:00 +0000

This new plugin monitors the space occupied by snapshots on a volume in its first stage of development. It is similar to its ZAPI predecessor check_netapp_pro.pl Snapshots in that it can calculate the space required by snapshots either relative to the volume size or the snapshot reserve. The parameter --base=volume|reserve is responsible for this.

Syntax and Options

With many options like --base=volume|reserve or --include/exclude=<regex> the check can be tailored to the needs of your organisation. Please have a look at the checks documentation page for explanations and examples.

Check for missing (accidentally deleted) volumes

Mon, 15 Nov 2021 00:00:00 +0000

The new check_netapp_volume missing plugin notifies you or your team, when a volume has been removed from the system.

Motivation and Workflow

NetApp has a “recovery queue” which is set to 12 hours by default. If the monitoring reports that a volume has been deleted, you have the chance to recover that volume.

Please check out the plugin’s Documentation Page for more details on how to implement this check into your monitoring framework and business-processes.

RESTful volume check for NetApps ONTAP filer

Tue, 27 Jul 2021 00:00:00 +0000

The v1.2.0 release of our Check NetApp-REST product contains a new monitoring plugin called check_netapp_volume usage. It provides the monitoring of:

the used space of each volume (in Bytes)
the total used space of several volumes
the average used space of several volumes
the min/max of used space of several volumes

A typical output would look like:

$ check_netapp_volume usage -H filer -w 30GiB -c 50GiB
NETAPP VOLUME USAGE OK - 5 volumes checked
vserv_b.vol2: 1.254MiB
vserv_b.vol1: 1.23MiB
vserv_a.vol1: 1.184MiB
vserv_b.vol0: 1.27MiB
vserv_a.vol0: 1.238MiB
| 'vserv_a.vol0'=1298432B;32212254720;53687091200;0; 'vserv_b.vol0'=1331200B;32212254720;53687091200;0; 'vserv_a.vol1'=1241088B;32212254720;53687091200;0; 'vserv_b.vol1'=1290240B;32212254720;53687091200;0; 'vserv_b.vol2'=1314816B;32212254720;53687091200;0;

Reporting on groups of volumes

To get the sum of all used-space on all volumes use the aggregated subcommand:

EMS Log-Monitoring

Mon, 21 Jun 2021 00:00:00 +0000

How to integrate the EMS-Log into an existing System-Monitoring solution

In this article ONTAP REST APIs: Automate Notification of High-Severity Events Mahalakshmi describes how to use messages to get notified about system events, depending on their type and severity. It’s a really flexible and comprehensive way to monitor NetApps ONTAP.

What if you already have a system-monitoring solution like Nagios, Icinga, op5 Monitor or Shinken in place? In that case the destinations (the recipients of the notifications) are already defined in the monitoring system. So all you need is a monitoring-plugin which does the filtering-part.

RESTfull Disk Check for NetApp's Ontap

Fri, 18 Jun 2021 00:00:00 +0000

The family of Check NetApp REST monitoring plugins has grown. With the check_netapp_disk container-type plugin the storage admin has a constant eye on disks that have been moved into unwanted containers.

Let’s look at an example:

.$ check_netapp_disk container-type -H sim96
NETAPP DISK CONTAINER TYPE OK - 28 disks checked
sim96cluster-01.NET-1.28: spare
sim96cluster-01.NET-1.27: spare
sim96cluster-01.NET-1.26: aggregate
sim96cluster-01.NET-1.25: aggregate
sim96cluster-01.NET-1.24: aggregate
sim96cluster-01.NET-1.23: aggregate
sim96cluster-01.NET-1.22: aggregate
sim96cluster-01.NET-1.21: aggregate
sim96cluster-01.NET-1.20: aggregate
sim96cluster-01.NET-1.19: spare
sim96cluster-01.NET-1.18: spare
sim96cluster-01.NET-1.17: aggregate
sim96cluster-01.NET-1.16: aggregate
sim96cluster-01.NET-1.15: aggregate
sim96cluster-01.NET-1.14: aggregate
sim96cluster-01.NET-1.13: aggregate
sim96cluster-01.NET-1.12: aggregate
sim96cluster-01.NET-1.11: aggregate
sim96cluster-01.NET-1.10: aggregate
sim96cluster-01.NET-1.9: aggregate
sim96cluster-01.NET-1.8: aggregate
sim96cluster-01.NET-1.7: aggregate
sim96cluster-01.NET-1.6: spare
sim96cluster-01.NET-1.5: spare
sim96cluster-01.NET-1.4: spare
sim96cluster-01.NET-1.3: aggregate
sim96cluster-01.NET-1.2: aggregate
sim96cluster-01.NET-1.1: aggregate

On this filer (it is a simulator) we have 28 disks. All disks are in either the aggregate or the spare container. Using the default switch of --ok-type=^aggregate|spare$ the check is OK.