|Component||Checks & Agents|
|Title||esx_vsphere_counters: no longer raise false alarms because of invalid data from ESX Host|
|Checkmk Edition||Checkmk Raw Edition (CRE)|
|Compatibility||Compatible - no manual interaction needed|
Sometimes the ESX Host does not report valid counter ids.
It may look like
If this happens the <<
>>section in the agent is empty. Any checks which relied on this section are now able to handle this scenario by raising a MKCounterWrappedException. Therefore these checks will no longer go UNKNOWN, but stale...