I need to know the exact API call that is being made to Nutanix from the nutanix_monitor probe to gather these data:

Cluster.Cluster_Num_Outstanding_Alerts
Hosts.Host_Num_Outstanding_Alerts
Disks.StorageCapacity

If possible, we would like to know the response that the nutanix_monitor probe is looking for as well. I am working with multiple Nutanix resources because we are getting these alarms for missing data:

Self-Monitoring Failures for 'pbnx-XXXXCLUS:Cluster.Cluster_Num_Outstanding_Alerts': Data Collection (1 of 1 failed).  See nutanix_monitor.log for more details
Self-Monitoring Failures for 'pbnx-XXXXCLUS:Hosts.Host_Num_Outstanding_Alerts': Data Collection (3 of 3 failed).  See nutanix_monitor.log for more details

Our logs show that Nimsoft is getting "null" values:

Jun 09 09:53:16:211 [BulkSender Monitor, nutanix_monitor] Sent NimQoS QOS_NUTANIX_CLUSTER_ALERT_COUNT D, source=XXXXCLUS, target=XXXXCLUS, measuretime=1591710795219, value=null, stdev=0.0 and received confirmation id BF67958868-65137

Jun 09 10:00:16:437 [BulkSender Monitor, nutanix_monitor] Sent NimQoS QOS_NUTANIX_HOST_ALERT_COUNT D, source=PRxxxxxxxx04.xxxxxxxank.com, target=PRxxxxxxxx04.xxxxxxxank.com, measuretime=1591711215317, value=null, stdev=0.0 and received confirmation id BF67958868-65686

However, from looking internally at the Nutanix API Explorer, there values ARE being reported, and Nimsoft is not picking them up.

- "Monitor Nutanix Alerts" box was not checked on the profiles. 

Release : 8.51

Component : UIM - NUTANIX

As per the nutanix_monitor log:

Jun 24 09:26:22:753 [Data Collector - xxxx-prodclus, nutanix_monitor] Number of Clusters: 1
Jun 24 09:26:22:953 [Data Collector - xxxx-prodclus, nutanix_monitor] Number of Hosts: 3
Jun 24 09:26:23:161 [Data Collector - xxxx-prodclus, nutanix_monitor] Number of Disks: 24
Jun 24 09:26:23:322 [Data Collector - xxxx-prodclus, nutanix_monitor] Number of Storage Containers: 3
Jun 24 09:26:23:322 [Data Collector - xxxx-prodclus, nutanix_monitor] *** Nutanix Alert monitoring not enabled

"Monitor Nutanix Alerts" box was not checked on the profiles. Customer went back to the original hub, checked the box, and validated that the json file was now being created with the API response, and the self-monitoring failure alarms have ceased.

When Data/Alarms are set to On, but that box is not checked, a null value is recorded because there's no file for the probe to read the response from. Customer had also not checked the "Monitor VMs" and "Monitor Controller VMs" options.