Return
-
Title
VMW Virtual Machine CPU Utilization fires alarms with low percentages -
Description
Alarms with low values can be seen, as an example below:
CPU Utilization.Unusual CPU utilization: 9%. Virtual machine "x" is outside the normal range of CPU utilization. -
Cause
Out of the box, it does not just evaluate the thresholds of warning 80% and critical 90%, you will see alarms for lower values because it also uses Standard Deviation for evaluation and that is an expected behavior, this is by design -
Resolution
Resolution:
In order to get alarmed just based on the thresholds, you will need to simplify the rule, If you don't want to be alerted for spikes.
Note: It's better if you create a copy of the original Rule, disable the original and modify the copy, in case you need to reverse any changes. The changes can be done like this:1. By going to Administration │ Rules & Notifications │ RulesHaving selected Cartridge: Virtual-VMware2. Do a search for "VMW Virtual Machine CPU Utilization", click on it and choose "View and Edit" and click on "Rule Editor", then under "Conditions, Alarms & Actions" do changes for both "Critical" and "Warning"You can replace the original logic with the below:if(#utilization from $scope.hostCPUs # > registry("VMW:virtualMachineCPU.critical")) return true; else return false;Note: Virtual-VMware-Intelliprofile has another rule for CPU Utilization but but does not have thresholds.You can also reference KB on how Standard deviation work: -
Additional Information
Reference: VMW Virtual Machine CPU Utilization - script