We have upgraded from 8.2.3 to 8.3.2P6 recently
Since then we can no longer get the node name when making queries to the API from our monitoring tool.
We use SPLUNK and this impacts our monitoring signficantly, as we can no longer get system stats.
Within SPLUNK the SystemPerfHandler throws a query to the target filer: https://<server>/servlets/netapp.servlets.admin.XMLrequest_filer with a the following content:
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_filer.dtd'>
<netapp version="1.13" xmlns="http://www.netapp.com/filer/admin">
8.2.3 the query returrns
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'>
<netapp version='1.21' xmlns='http://www.netapp.com/filer/admin'>
8.3 returns something a little different:
<netapp version='1.32' xmlns='http://www.netapp.com/filer/admin'>
What has changed and what should the query be to return each node name?
I have a case open with netapp and splunk, but am wondering if the wider community has come across this issue.
See The Solution
I think you might need to change the value of the "objectname" property in your API call to "system:node" in 8.3+.
This will ensure the API call returns each node in your cluster as it did in 8.2. EG:
If you set "objectname" property to "system" it will just return the cluster UUID instead of the each node in the cluster as it previously did. EG:
To see what objectnames are available you can call the "perf-object-list-info" API. I hope this helps?
View solution in original post
NetApp Wins One Silver and One Bronze Stevie® Award in 2022 Stevie Awards for Sales and Customer Service
Live Chat, Watch Parties, and More!
Engage digitally throughout the sales process, from product discovery to conﬁguration, and handle all your post-purchase needs.