Branch: refs/heads/master
Home:
https://github.com/Checkmk/checkmk
Commit: a67f6fd46afb5d76b0eebd5315f254fcb689ea16
https://github.com/Checkmk/checkmk/commit/a67f6fd46afb5d76b0eebd5315f254fcb…
Author: Moritz Kiemer <moritz.kiemer(a)checkmk.com>
Date: 2024-01-23 (Tue, 23 Jan 2024)
Changed paths:
M packages/cmk-agent-based/cmk/agent_based/v2/_check_levels.py
Log Message:
-----------
fix accidental or-ing
Change-Id: I2ff7d10442a79ac763db880bcb3e205f4ce6952f
Commit: e7cfa729d3dbf829a46988c41a6e38c2491883ad
https://github.com/Checkmk/checkmk/commit/e7cfa729d3dbf829a46988c41a6e38c24…
Author: Moritz Kiemer <moritz.kiemer(a)checkmk.com>
Date: 2024-01-23 (Tue, 23 Jan 2024)
Changed paths:
M packages/cmk-agent-based/cmk/agent_based/v2/_check_levels.py
M packages/cmk-agent-based/tests/cmk/agent_based/v2/test_check_levels.py
Log Message:
-----------
check levels: consistently create both metrics
With this we make the creation of the prediction
metrics more consistent:
The metric for lower levels is always called
'predict_lower_<name>', regardless of whether the
upper levels are predictive or not.
Both prediction metrics are recorded if present,
even if they are the same.
While it is nice to conslidate the output (for
human consumption) there is no benefit in not adding
the value to the RRD.
Change-Id: I7e73a05f51cbedf353e53b2a70a45053a6a1d921
Compare:
https://github.com/Checkmk/checkmk/compare/2b8d15c24523...e7cfa729d3db