Module: check_mk
Branch: master
Commit: 8b28cb94e8f6725f5b91825738f478423bf18081
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=8b28cb94e8f672…
Author: Óscar Nájera <on(a)mathias-kettner.de>
Date: Fri Oct 26 16:20:27 2018 +0200
6646 FIX CPU utilization per process can be weighted by total CPU number
Processes that where monitored on CPU utilization did not have a consistent
behavior. On windows systems 100% CPU utilization implied all cores in the
system where at max load. On other systems every core contributed with a
100% at full load, thus the maximum load was N*100%.
This was also inconsistent with the system wide CPU utilization check
where, 100% is all cores at full load.
Consistency is brought is this werk, where 100% is all cores at full load
by default. For backwards compatibility with previous configurations, where
threshold rules where explicitly configured, the old behavior continues to
be used until the user explicitly chooses a particular behavior.
This option is available under CPU rescale maximum load in the process
discovery rules.
CMK-695
Change-Id: I63d420c74f2bbf762dec4615b49518e03e32404e
---
.werks/6646 | 24 +++++++
checks/ps | 2 +-
checks/ps.include | 46 +++++++++----
cmk/gui/plugins/wato/check_parameters.py | 35 +++++++---
tests/unit/checks/test_ps.py | 109 ++++++++++++++++++++++++++-----
5 files changed, 177 insertions(+), 39 deletions(-)
Diff:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=8b28cb94e8…