The failure is basically that the vsphere.virtualmachine.cpu.total.mhz and sphere.virtualmachine.cpu.free.mhz fields do not record information in a large number of documents, while in another, these metrics are received.
validate the integration documentation, where the fields in question are seen: exported-fields-vsphere
We believe that it is a bug present in the integration version, since we do not receive error logs in the associated Elastic Agent.
{"log.level":"debug","@timestamp":"2024-07-31T21:32:32.101Z","message":"custom fields not activated or custom values not found/parse in Summary data. This is either a parsing error from vsphere library, an error trying to reach host/guest or incomplete information returned from host/guest","component":{"binary":"metricbeat","dataset":"elastic_agent.metricbeat","id":"vsphere/metrics-default","type":"vsphere/metrics"},"log":{"source":"vsphere/metrics-default"}
No filter with fields
with filter checking absence of fields in logs
Only 105 documents found containing vsphere.virtualmachine.cpu.total.mhz: * or vsphere.virtualmachine.cpu.free.mhz: *