[checkmk-commits] [tribe29/checkmk] b6908a: 10308 FIX Recover performance data output for aver...

Branch: refs/heads/1.5.0 Home: https://github.com/tribe29/checkmk Commit: b6908ac5bc776cb0ca91679a836fc0d859ae1c92 https://github.com/tribe29/checkmk/commit/b6908ac5bc776cb0ca91679a836fc0d85… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2019-10-22 (Tue, 22 Oct 2019) Changed paths: A .werks/10308 M checks/if.include Log Message: ----------- 10308 FIX Recover performance data output for averaged bandwidth use in IF checks Revert "7449 FIX Remove spurious perfdata in IF checks for in/out". Average perfdata was removed unwantedly This reverts commit c3f4e756f2bb2350811df3a27be435ee3c9e01bc. Change-Id: Ifde61e4f0628340bd26f780c393d85c5b7c87023 Commit: 0ae0656a4480737b724768817eb20947c0fff2dd https://github.com/tribe29/checkmk/commit/0ae0656a4480737b724768817eb20947c… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2019-10-22 (Tue, 22 Oct 2019) Changed paths: A .werks/10309 M cmk_base/prediction.py Log Message: ----------- 10309 FIX Predictive Levels is robust against receiving no data at all On a new site, when perfdata is not available and predictive levels are set. Livestatus replies with [0, 0, 0] -> step==0, and a zero division Error is raised leaving Check in UNKN and no new perfdata is delivered, which makes the problem permanent. Extra flow control on retrieved data allows for the predictive levels not to be calculated until there is enough data available. The check now continues to output such data. Change-Id: I2778e4929b86476db214ba48b5603e0acd662cb7 Compare: https://github.com/tribe29/checkmk/compare/b0deb1bddd94...0ae0656a4480