[checkmk-commits] [tribe29/checkmk] 7ceede: 11096 hyperv_vms: use default levels instead of di...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 7ceede416b890f3e6bc98a3fa69b1d8f6ea82e65 https://github.com/tribe29/checkmk/commit/7ceede416b890f3e6bc98a3fa69b1d8f6… Author: Joerg Herbel <joerg.herbel(a)tribe29.com> Date: 2020-05-14 (Thu, 14 May 2020) Changed paths: A .werks/11096 M checkman/hyperv_vms M checks/hyperv_vms M cmk/gui/plugins/wato/check_parameters/hyperv_vms.py M locale/de/LC_MESSAGES/multisite.po M tests-py3/unit/checks/generictests/datasets/hyperv_vms.py Log Message: ----------- 11096 hyperv_vms: use default levels instead of discovered state The check hyperv_vms now uses a set of default levels to map the state of VMs to monitoring states. Before, by default, the check compared the current VM state against the state at the point when the service was discovered and went CRIT if the two states did not match. This behavior is still available, but the check now has to be specifically configured to do this, see the rule "State of Microsoft Hyper-V Server VMs". Furthermore, the check now always works when executed as a manual check. Before, it might have crashed in this case, depending on the used configuration. This change is incompatible in the sense that users have to adjust the rules for this check to make it behave the way it did before. Change-Id: Id4864f2f5dae5d472d87ba0596498c0f82391644 Commit: 0b2ef11077846f356b99f438562080afc91c857d https://github.com/tribe29/checkmk/commit/0b2ef11077846f356b99f438562080afc… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-05-14 (Thu, 14 May 2020) Changed paths: M cmk/base/config.py Log Message: ----------- CheckAPI: tiny bug fix Change-Id: I2711872ab687d2618b1385911ad826c71f1fd244 Compare: https://github.com/tribe29/checkmk/compare/ae4dcb97c867...0b2ef1107784