netapp_ontap_rest probe: False Self-Monitoring alarms for legacy system_ops and http_ops metrics

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The netapp_ontap_rest probe (v.1.0.3.* and patches) may generate frequent self-monitoring alarms regarding failed data collection for specific metrics, even when general discovery and monitoring are working correctly.

Symptoms

Self-monitoring alarms are received with messages similar to:

• Self-Monitoring Failures for '###:SYSTEM.system_ops': Data Collection (1 of 1 failed). See netapp_ontap_rest.log
• Self-Monitoring Failures for '###:SYSTEM.http_ops': Data Collection (1 of 1 failed). See netapp_ontap_rest.log

Environment

• DX Unified Infrastructure Management (UIM) 23.4.*
• netapp_ontap_rest probe version 1.0.3 or lower
• NetApp ONTAP 9.16.1P8 or higher (and systems with varied API configurations)

Cause

These alarms relate to legacy metrics (system_ops and http_ops) that were part of the older NetApp ONTAPI (ZAPI) framework used by the legacy netapp_ontap probe.

In modern NetApp REST API architectures, these metric names have been deprecated and removed, replaced by:

• iops.other
• iops.read
• iops.write
• iops.total

The netapp_ontap_rest probe contains leftover configurations for these legacy metrics for backward compatibility. Because the NetApp system no longer exposes these specific counters, the probe's self-monitoring identifies the missing data as a collection failure and triggers an alarm.

Resolution

This issue is addressed in the build attached to this KB: Error: netapp_ontap_rest probe fails with 401 Unauthorized or 400 Bad Request due to ONTAP API