When monitoring NetApp ONTAP clusters ranging from versions 9.6 to 9.17.1, the netapp_ontap_rest probe may encounter connection or data retrieval failures. This occurs because certain metric fields or counters have evolved, changed availability, or been deprecated in newer ONTAP API schemas, requiring more adaptive handling by the probe.
The netapp_ontap_rest probe fails to successfully collect data from the NetApp system. The following errors are observed in the probe logs:
Status code: 401 / Non-200 status code: 401HTTP 400 Bad Request for URL: .../api/cluster/counter/tables/...Error Message: The value "key" is invalid for field "fields"Note: Connectivity via curl from the same robot using identical credentials and certificates completes successfully.
NetApp ONTAP environments span a wide range of versions where API schemas, counter tables, and field availability can vary significantly or depend on specific cluster configurations.
An issue (tracked via DE675876) was identified where the probe requested specific legacy or default fields (such as "key") that are either unconfigured, restricted, or no longer recognized by the API of certain modern ONTAP versions. When encountering these unexpected schema differences, the NetApp system rejects the request, throwing a 400 Bad Request or 401 Unauthorized error.
The attached patch fixes the issue netapp_ontap_rest-1.0.4-20260730.091603-9.zip
1. Download the package
2. Deploy on the natapp_ontap_rest robot
3. Verify if the issue still exists
If the issue persists after upgrading to version netapp_ontap_rest-1.0.4-20260730.091603-9.zip, verify:
Additional changes in this build related to Metrics:
1. Volume Snapshot Free Capacity / Snapshot Used Capacity %
These two metrics were not being collected because the probe was looking for slightly different field names than what your ONTAP version actually returns. We identified the correct field names directly from your system's own API responses and updated the probe to match.
Both metrics should now report real values on every collection cycle.
2. Aggregate Snapshot Available Capacity
We updated the probe so this metric always publishes a value (defaulting to zero when there's nothing to calculate) rather than occasionally appearing blank, which is what may trigger an alarm.
3. Enclosure Temperature
Temperature reporting for shelf enclosures varies by ONTAP version and shelf model. We've built in a more resilient collection path that checks multiple sources for this reading and, if none are available on a given cycle, reports a clear default value rather than leaving the metric blank.