Getting HA partner info for node in ZAPI

[limpid ferry]

We had a custom_node.yaml file working fine in the Rest collector that add HA partner info to the exported fields. However, due to the guidance in the release notes to de-prioritize Rest until 9.12 because of burt 1585893, we now need to get those fields in the Zapi node.yaml file.

It looks like while https://docs.netapp.com/us-en/ontap-restmap-991/system.html#system-get-node-info-iter has the partner info, system-node-get-iter does not. At first I thought maybe recreating the node.yaml file using system-get-node-info-iter query would work, but it's missing quite a few of the fields.

What might be the best approach to get the HA partner fields in the Zapi exported fields for node like we had with the Rest version?

Getting HA partner info for node in ZAPI

[split seal]

@limpid ferry Could you share the custom_node.yaml file? Check to see if the cf-get-iter ZAPI helps. Burt issue 1585893 is about RestPerf calls. I believe you are using a Rest collector for the custom_node.yaml file, so this Burt should not be applicable to such calls.

[limpid ferry]

Ah, well that makes it easier. I misunderstood and thought we had to disable all Rest lol.

So we would be fine to do this then?

collectors:

• Rest
• Zapi
• ZapiPerf
• Ems
• RestPerf

[limpid ferry]

@split seal It may take a few weeks for the upgrade to get through QA etc so I will need to proceed with the custom_node.yaml file in Zapi approach to get the custom fields back faster. Trying to make a custom metric using a different Zapi query as we've discussed and merging / joining somehow via custom_node.yaml plugin section. Attached is what I had for the Rest collector as asked

[covert fern]

yes that will work fine - running both REST and ZAPI collectors at the same time are explained here https://netapp.github.io/harvest/nightly/architecture/rest-strategy/#can-i-use-the-rest-and-zapi-collectors-at-the-same-time

[split seal]

@limpid ferry The REST Collector has parity with Zapi Collector starting from ONTAP version 9.12. Therefore, if you're running on an ONTAP version earlier than 9.12 and you're using the REST precedence over Zapi, you might not be able to access all metrics that are available through the Zapi Collector.

[limpid ferry]

Opposite problem, really. Because we had to de-prioritize Rest to deal with Issue 2262, and have to wait a few weeks to get the upgrade in place, I have to get HA partner info into node_labels, which was easy in Rest Collector. I'm having to figure out some gymnastics to accomplish the same with Zapi custom_node.yaml

[covert fern]

@limpid ferry another option if ZAPI gymnastics don't pan out, you can disable all the rest objects in conf/rest/default.yaml except for your REST custom_node and then use a set of collectors like:

• Rest
• Zapi
• ZapiPerf
• Ems

[limpid ferry]

Hm, true, it was really the volume metrics that got messed up and not the node

[limpid ferry]

@covert fern yeah I just tested that, commented everything out except for the custom node and it works fine, I'm done trying to fight with Zapi lol

[split seal]

@limpid ferry If you think that we should add HA details in Harvest, Could you open a feature request for adding HA details for a node in harvest? Thanks.

[split seal]

opened a issue to track here https://github.com/NetApp/harvest/issues/2611