[ESX 8 API]get_esx_stats function failed to retrieve stats

Hi ​@blank ,

I’m not a VMware expert but the following error come from your vCenter:

{
  "messages": [
    {
      "args": [],
      "default_message": "Unable to create Acquisition Spec due to conflict at row: `375`",
      "localized": "Unable to create Acquisition Spec due to conflict at row: `375`",
      "id": "com.vmware.vstats.acq_specs_create_failed_conflict",
      "params": {
        "id": {
          "s": "375"
        }
      }
    }
  ]
}

Do you have access to the vCenter logs?

Did you update the vCenter version recently?

i have ma de some tests:

added monitoring account to vcenter admin group > same problem

test service with vcenter admin not same error but ar least il start workin with my monitoring account few seconds after :

 

/usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=swap --hostname='mgt-vcenter.admin.local' --port='443' --proto='https' --esx-name='***esx***' --esx-id='host-707608'
 --username='ce***@vsphere.local' --password='***'  --warning-read-rate-bps='' --critical-read-rate-bps='' --warning-write-rate-bps='' --critical-write-rate-bps='' --warning-usage-bytes='' --critical-usage-bytes='' --warning-usage-prct='' --critical-usage-prct=''
UNKNOWN: no data for resource host-707608 counter mem.swap.current.HOST at the moment. - no data for resource host-707608 counter mem.swap.target.HOST at the moment.
 - get_esx_stats function failed to retrieve stats
The counter mem.swap.current.HOST was not recorded for resource host-707608 before. It will now (creating acq_spec).
The counter mem.swap.target.HOST was not recorded for resource host-707608 before. It will now (creating acq_spec).

 /usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=swap --hostname='mgt-vcenter.admin.local' --port='443' --proto='https' --esx-name='***esx***' --esx-id='host-707608'
 --username='adm**@vsphere.local' --password='***' --warning-read-rate-bps='' --critical-read-rate-bps='' --warning-write-rate-bps='' --critical-write-rate-bps='' --warning-usage-bytes='' --critical-usage-bytes='' --warning-usage-prct='' --critical-usage-prct=''
UNKNOWN: no data for resource host-707608 counter mem.swap.current.HOST at the moment. - no data for resource host-707608 counter mem.swap.target.HOST at the moment.
 - get_esx_stats function failed to retrieve stats
The acq_spec entry has to be extended to get more stats for host-707608 / mem.swap.current.HOST
The acq_spec entry has to be extended to get more stats for host-707608 / mem.swap.target.HOST

/usr/lib/centreon/plugins/centreon_vmware8_esx_restapi.pl --plugin=apps::vmware::vsphere8::esx::plugin --mode=swap --hostname='mgt-vcenter.admin.local' --port='443' --proto='https' --esx-name='***esx***' --esx-id='host-707608'
 --username='ce***@vsphere.local' --password='***'  --warning-read-rate-bps='' --critical-read-rate-bps='' --warning-write-rate-bps='' --critical-write-rate-bps='' --warning-usage-bytes='' --critical-usage-bytes='' --warning-usage-prct='' --critical-usage-prct=''
OK: Swap usage: 0.00 B (max available is 0.00 B), Percent used: 0.00% | 'swap.usage.bytes'=0B;;;;0 'swap.usage.percent'=0%;;;0;100

 

Hi ​@blank,

First, a short explanation of how the statistics are made available in VMware API and then my interpretation of the behaviour you describe.

How it works

One has to create an entry in the acq_specs endpoint to be able to then collect data from /data/dp. These entries have an expiration date after which they need to be refreshed to make data collectable again.

My guess

The first account may not be able to list the existing acq_specs, so the plugin tries to create it again, but as it already exists (but has expired) the creation fails.

The second account has the ability to view the existing acq_spec, so it tries to update it and it succeeds.

Does my interpretation look relevant to you?

If so, I’d be interested to investigate with you to find out which privileges could be missing to your first account.

i’m ok with that, i can confirm it maybe begin next week if my services stall again. By the way, i was using the old plugin with the same account, i have just removed it from readonly group ann added to vstatsuser and if i remember; check have start working without using the admin account. I’ll check in release note if there is something can match the problem.