We've encountered a problem with the SOAP API in NetApp ONTAP. The data displayed in the NetApp ONTAP System Manager(UI) doesn't align with the data we retrieve from the SOAP API. Our specific concern is related to latency data that we want to monitor. However, the data from the SOAP API consistently differs from what's presented in the NetApp ONTAP System Manager.
API request
URI: <ONTAP_CLUSTER>/servlets/netapp.servlets.admin.XMLrequest_filer
Request body:
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'>
<netapp version='1.170' xmlns='http://www.netapp.com/filer/admin'>
<perf-object-get-instances>
<objectname>volume</objectname>
<counters>
<counter>write_latency</counter>
<counter>read_latency</counter>
<counter>avg_latency</counter>
</counters>
<instances>
<instance>MT_Vol10</instance>
</instances>
</perf-object-get-instances>
</netapp>
Response body:
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE netapp SYSTEM 'file:/etc/netapp_gx.dtd'>
<netapp version='1.170' xmlns='http://www.netapp.com/filer/admin'>
<results status="passed">
<instances>
<instance-data>
<counters>
<counter-data>
<name>avg_latency</name>
<value>233356</value>
</counter-data>
<counter-data>
<name>read_latency</name>
<value>6500</value>
</counter-data>
<counter-data>
<name>write_latency</name>
<value>0</value>
</counter-data>
</counters>
<name>MT_Vol10</name>
<sort-id>0</sort-id>
<uuid>random-id</uuid>
</instance-data>
</instances>
<timestamp>1697023819</timestamp>
</results>
</netapp>
ONTAP System Manager Image
In the provided image from the System Manager, the latency value appears as 0, while the response from the SOAP API indicates a latency of 6500.
