With the next release, the c****dot performance getter will ignore temporary volumes. Temporary volumes are created in the background when moving volumes between aggregates, for instance. These volumes can lead to a UNKNOWN or an „out of bounds“ result for the performance checks and UsageTrend because these instances …
The Input-/Output Operations per Second (IOPS) or Operations per Second (OPS) can be monitored on various levels:
System Operations (total_ops) This is why the counter total_ops in the PerfSys check exists. Unfortunately, this counter is deprecated and will no longer be supported by NetApp in new versions of DataONTAP. …
A first test version of our new check check_netapp_events to monitor **the **ASUP logs is available upon request. Please get in contact with us directly , this check is not yet available for distrubution. The check is _not_part of our **check_netapp_pro **suite and in technical terms is completely independent. Our …
The most common error messages that occur during fresh installations are those related to the performance data collected by the getters. Previously, they only contained the information that the delta of the check is too big or too small for the interval, with which the getter collects the data and that the settings …
With our default configuration a scrub is executed on the filers of aggregates. In some cases, the scrub and fix might not be able finish on time in the designated period. This results in warnings such as:``` filer1::> aggr scrub -aggregate * -action status Raid Group:/aggr0_01/plex0/rg0, Is Suspended:false, Last …
In my articles Overly Long Outputs and Turning Off Performance Data Output I discuss shortened text outputs. However some basics about the subject matter are needed in order to fully understand these two articles The first thing to know is that the plugin should provide data to the monitoring system that is is …
We are currently thinking of developing a check that sends a warning when volumes appear on a filer that are not protected by a SnapVault or SnapMirror relationship. This way, the following scenario should be identified before any loss of data can occur: Somebody creates a primary volume and forgets to save it with a …
Sis is a new check we are releasing to identify deduplication problems. The check monitors stale-fingerprint-percentage and run-time of the last successful reduplication process. It will be available in the next unstable version 3.6.0_11.
The switch --perf_data_prefix|–perf_data_multiplicator|–perf_data_factor used to set SI-Prefixes (ki, k, Mi, M, Gi, G, …) for performance data will be removed with the next release. From then on, the respective basic units (bits, bytes, seconds, …) will be used for performance data output (currently, this …
We updated our snapshots check so that the ‑‑node|‑‑vserver|‑s switch is no longer required. Like many other checks, this check will inspect all snapshots on all volumes for every Vserver on the filer if the Vserver name is not specified. This change will be included in the next unstable release.