High cpu ready values are probably the single most recognised sign that a virtual machine is having problems, whether due to application issues, or cpu undersizing, the vSphere admin should know about it.
Setting an alarm for this is so simple and flushes out the bad boys.
The suggested settings are from VMware, 20% and 40%*.
Before applying you should run powercli-get-vmreadyspikesforxdays so you know if these values are going to create an alarm storm.
*The general accepted value is >5% is undesirable, >10% is bad
When ready times exceed the trigger value an alarm will appear