Assert CPU % values in the CPU check #859

alq666 opened this Issue Mar 10, 2014 · 3 comments


None yet

3 participants

alq666 commented Mar 10, 2014

We have seen cases of abnormal values (> 100%). Regardless of the cause we can and should assert that CPU/disk/memory percentages 0 <= x <= 100%.

@alq666 alq666 added checks triage 0 - Backlog and removed triage labels Mar 10, 2014
alq666 commented Mar 10, 2014

Related to #653


The values returned by WMI often add up to > 100% so I think if we added such an assertion we would drop points often. I believe this may have been caused by a bug in WMI or how these values are reported, but I'll have to see if I can find the source for that.

@remh remh added this to the 4.3.x milestone Mar 10, 2014
@remh remh modified the milestone: 5.1.0, 4.3.x May 8, 2014
@remh remh modified the milestone: Future, 5.1.0 Sep 26, 2014
remh commented Jan 5, 2016

We haven't seen these cases since we bundle our own version of sysstat. Closing.

@remh remh closed this Jan 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment