VMware probe - vCenters in profile pending state
Article ID: 265104
Updated On:
Products
Issue/Introduction
VMware probe profiles remaining in a pending state for long periods of time can be attributed to several reasons.
- Incorrect sizing
- Lack of sufficient java memory configured in the VMware probe
- Error/issues on the vCenter side with solutions that are well documented by VMware in their community forum
- Busy vCenters that would benefit by splitting up the monitoring across multiple VMware probe instances
Environment
- VMware probe, any version
- Release: 20.4
Resolution
Review the CPU and ensure the processor speed is at the recommended level 3 GHz or higher. Contact the VMware admin to see if increasing the number of processors is warranted.
In some cases where profiles remain in a pending state for a long time, a reboot of the vCenter was required to address multiple issues with the monitoring of the vCenter. After the vCenter was rebooted, all configured checkpoints were available on the VMware probe's Admin Console Configure Page once the monitored resource was successfully discovered by the probe.
Add another instance of the VMware probe specifically for the largest vCenter and move that monitoring with thousands of VMs to the new instance.
For the below error in the vmware log, this is a VMware vCenter error and has nothing to do with DX UIM so it must be resolved via the vCenter configuration.
[Performance Metric Collection - 24, vmware] Failed to execute single perf query for entity resgroup-742787. Invalid property: querySpec.interval Details: A specified parameter was not correct: querySpec.interval
In the VMware vSphere Client, connect to the vCenter Server and perform the following steps:
-
In the menu, choose Administration -> vCenter Server Settings.
-
In the vCenter Server Settings dialog box, select Statistics.
-
Ensure that the 5 minutes statistics interval (daily) is enabled.
Additional Information
Feedback
