Getting critical alerts quite often from rule: VMW Resource Pool Percent Ready
1. It fires alarms when VM requests CPU cycle from the ESX host: (Resource Pool Rules | VMW Resource Pool Percent Ready)
2. The alarm indicates that ESX server is busy, which couldn't allocate CPU cycles to the VM( that requests the ESX host) in the resource pool.
3. On the web console, check for the data as below:
Dashboards | Configuration | Data
Expand VMware -> Resource Pools
Click on CPU Percent Ready.
Per condition in the rule:
#cpuPercentReady# > registry("VMW:percentReady.critical")
It checks if the metric( cpuPercentReady ) is greater than the registry variable.
Then it fires an alarm.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center