The problem is it was not there before 2.1. We changed dashboard now from “service states” to “service hard states” and set hard state limit to 3 so it can fail 2 times till we get this warning, cause it is always missing just once. The next agent call wmi_cpuload (and it is ALWAYS only the cpuload) will be back. Regardless if it is direct on the server OR as piggyback. Problem now is we get warning for more critical services delayed by 3 minutes.