Werk #1102: esx_vsphere_counters: no longer raise false alarms because of invalid data from ESX Host
Component | Checks & agents | ||||||||||||||||||
Title | esx_vsphere_counters: no longer raise false alarms because of invalid data from ESX Host | ||||||||||||||||||
Date | Aug 28, 2014 | ||||||||||||||||||
Level | Trivial Change | ||||||||||||||||||
Class | Bug Fix | ||||||||||||||||||
Compatibility | Compatible - no manual interaction needed | ||||||||||||||||||
Checkmk versions & editions |
|
Sometimes the ESX Host does not report valid counter ids.
It may look like
<id>
<counterId>-2147483645</counterId>
<instance>84</instance>
</id>
If this happens the <<<esx_vsphere_counters>>> 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...