[checkmk-commits] [tribe29/checkmk] 413bbf: Reserved 30 Werk IDS

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 413bbf4d894a82ce7d8f0db3463b432f42c968f9 https://github.com/tribe29/checkmk/commit/413bbf4d894a82ce7d8f0db3463b432f4… Author: Andreas Boesl <andreas.boesl(a)tribe29.com> Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: M .werks/first_free Log Message: ----------- Reserved 30 Werk IDS Change-Id: I5e4aa8305e18ab3c3119a91f535d14b1bc02411e Commit: b2884dd6ccf5b6c65f4f165cad392f69db43b0ba https://github.com/tribe29/checkmk/commit/b2884dd6ccf5b6c65f4f165cad392f69d… Author: Wontek Hong <wontek.hong(a)tribe29.com> Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: A .werks/10422 A checkman/cisco_cpu_memory A checks/cisco_cpu_memory M checks/cisco_mem.include M cmk/gui/plugins/metrics/check_mk.py A cmk/gui/plugins/wato/check_parameters/cisco_cpu_memory.py A tests/unit/checks/generictests/datasets/cisco_cpu_memory.py M tests/unit/checks/generictests/datasets/cisco_mem.py M tests/unit/checks/generictests/datasets/cisco_mem_asa64_5c2e2c9a3a465_regression.py Log Message: ----------- 10422 cisco_cpu_memory: Check for monitoring CPU Memory of Cisco devices This check monitors the CPU Memory level of Cisco devices. A Wato rule can be configured depending on free or occupied memory. The details displayed on the service depend on this WATO rule with the default being free memory. The performance graph will always be based on occupied memory. Change-Id: I3c35c4a40082aaa33f085bca63d258b4a9a13c36 Commit: 8a4394a4bbe8da412e32b2527614384cca0b803f https://github.com/tribe29/checkmk/commit/8a4394a4bbe8da412e32b2527614384cc… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: A .werks/10402 M cmk/utils/prediction.py M tests/unit/cmk/utils/test_prediction_commons.py Log Message: ----------- 10402 FIX Deal with RRD sources which are not updated anymore in multiline graphs The metrics "Guest operating systems" and "CPU time stolen by other operating systems" that appear on the CPU utilization service Check for unix systems are only relevant on virtualized environments. On other cases they are always zero, and thus completely skipped in the graphs, but still tracked by the monitoring core. Checkmk 1.6 stopped delivering this metrics for systems where they are irrelevant. This saves disk space, and disk I/O improving scalability. If you update from Checkmk 1.5, the unused RRDs will remain in disk but won't be updated anymore. If you use the RRD single format you wont experience any problem, but if you are on RRD format for one RRD per metric, the RRDs will go out of sync. At the time of drawing the graphs, this lack of syncronicity will disrupt the resolution of the data, and crash the graphs, if two metrics have a different resolution. With this werk, data is resampled after being retrieved from the core if the metrics on the same graph have different resolutions. Change-Id: I2b563487dbe0915fb4b213285f0a25a1ebff2ea1 Compare: https://github.com/tribe29/checkmk/compare/71c9209b0a6a...8a4394a4bbe8