I fixed most of the things and when running the script with the "-v" switch I get:
Skipping send: no graphite root defined
Could that explain why I see no data? Where do I need to define my server?
I see in the files there are parameters:
REQUIRED: _HARVEST_HOSTNAME - hostname/IP of ONTAP system _HARVEST_AUTH_TYPE - either "password" (default) or "ssl_cert" _HARVEST_CLUSTER - Name of ONTAP Cluster _HARVEST_GRAPHITE_ROOT - prefix of metric path in Graphite (e.g.: 'netapp.capacity.GROUP.CLUSTER'), if prefix is "_", data will be collected but not sent to Graphite.
Do I need to define them in each script? They don't inherit the info from the "old" harvest?
Also, do i need to schedule the scripts to be run separately or will they be run automatically by the "old" Harvest? I already ran the harvest script:
It seems like SVM-DR SnapMirror relationships are not supported by the SnapMirror extension and only Volume SnapMirror is supported? I'm getting a lot of this in the log file (we're purely an SVM-DR shop):
[2020-03-12 16:49:27,914] [WARNING] [poll_snapmirrors] Destination relationship with no node or volume. Skipping
[2020-03-12 16:49:27,914] [WARNING] [poll_snapmirrors] Source relationship with no volume. Skipping
The reason why we skip them now is that we want to summarize SnapMirrors relationships per node (to compare that against the active replications limit of each node). We can't associate an SVM(-DR)s to a Node, but we can sum up SnapMirrors under SVM as well.
It probably will require a 2-3 lines of additional code... So if you need that, let me know!
Sorry for such a late reply. I appreciate very much your willingness to share your work (and I share your sympathy for Perl!) Is it okay if I get back to you when we do our next release? We'll be happy to include your extension in our package (just make sure to add your name as author)!