[checkmk-commits] 6149 FIX ps: The linux ps check CPU utilization calculation changed since 1.4.0p27

Module: check_mk Branch: master Commit: 91a73809de4d34418985263413a794a984543d68 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=91a73809de4d34… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Tue May 22 11:57:48 2018 +0200 6149 FIX ps: The linux ps check CPU utilization calculation changed since 1.4.0p27 The calculation of the CPU utilization of processes on linux systems was not taking the number of CPU cores into account for a long time. This results in CPU utilizations reported with more than 100%, up to 100%*CPU-cores. For example in case 3 processes use 3 of 6 cores at 100%, this resulted in a usage of 300%. The intention of the change in 1.4.0p27 was to make the windows and linux ps checks both take the number of CPU cores into account and cap the usage at 100%. The problem with this change is that all possibly existing thresholds that have been configured for the old scheme will not work anymore with the new scheme. We have now reverted the changes version 1.4.0p27 introduced to get the old behavior back. In a future release, we will finally make the switch to the new scheme. But this will be done in a compatible way where the already configured thresholds will still work. Change-Id: Idac9be3065a594958125378a6de8e231b8b81467 --- .werks/6149 | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/.werks/6149 b/.werks/6149 new file mode 100644 index 0000000..7917062 --- /dev/null +++ b/.werks/6149 @@ -0,0 +1,24 @@ +Title: ps: The linux ps check CPU utilization calculation changed since 1.4.0p27 +Level: 1 +Component: checks +Class: fix +Compatible: compat +Edition: cre +State: unknown +Version: 1.6.0i1 +Date: 1526982355 + +The calculation of the CPU utilization of processes on linux systems was not taking the number +of CPU cores into account for a long time. This results in CPU utilizations reported with more +than 100%, up to 100%*CPU-cores. For example in case 3 processes use 3 of 6 cores at 100%, this +resulted in a usage of 300%. + +The intention of the change in 1.4.0p27 was to make the windows and linux ps checks both take +the number of CPU cores into account and cap the usage at 100%. The problem with this change is +that all possibly existing thresholds that have been configured for the old scheme will not +work anymore with the new scheme. + +We have now reverted the changes version 1.4.0p27 introduced to get the old behavior back. + +In a future release, we will finally make the switch to the new scheme. But this will be done +in a compatible way where the already configured thresholds will still work.