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

1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.5i6	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

Sometimes the ESX Host does not report valid counter ids.
It may look like

&lt;id&gt;
  &lt;counterId&gt;-2147483645&lt;/counterId&gt;
  &lt;instance&gt;84&lt;/instance&gt;
&lt;/id&gt;

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...

To the list of all Werks