[checkmk-commits] [tribe29/checkmk] a5bf30: 15155 FIX sap_hana_status: Handle WARNING status c...

Branch: refs/heads/2.2.0 Home: https://github.com/tribe29/checkmk Commit: a5bf30ca9e6c1773d793888c62ce7d3076057135 https://github.com/tribe29/checkmk/commit/a5bf30ca9e6c1773d793888c62ce7d307… Author: Sofia Colakovic <sofia.colakovic(a)tribe29.com> Date: 2023-03-08 (Wed, 08 Mar 2023) Changed paths: A .werks/15155 M cmk/base/plugins/agent_based/sap_hana_db_status.py M tests/unit/cmk/base/plugins/agent_based/test_sap_hana_db_status.py Log Message: ----------- 15155 FIX sap_hana_status: Handle WARNING status correctly Previously, SAP HANA Database Status service would go to CRIT in case of database status 'WARNING'. Now, the service goes to Checkmk state WARN. SUP-4970 Change-Id: I13653a4eed4d780817ab1749d8a2082bc7322be6 Commit: 378d799ea46f534887c72a1d39c21d17808cb664 https://github.com/tribe29/checkmk/commit/378d799ea46f534887c72a1d39c21d178… Author: Sofia Colakovic <sofia.colakovic(a)tribe29.com> Date: 2023-03-08 (Wed, 08 Mar 2023) Changed paths: A .werks/15153 M cmk/base/plugins/agent_based/azure_virtual_machine.py M cmk/gui/plugins/wato/check_parameters/azure.py M tests/unit/cmk/base/plugins/agent_based/test_azure_virtual_machine.py Log Message: ----------- FIX 15153 azure_virtual_machine: Redesign service rule Previously, if a mapping for power or provisioning states was configured for some, but not for all states, the unconfigured states would always be mapped to WARN. This behavior was confusing and forced the users to configure mapping for all the states even when they wanted to change the behavior of only one. Moreover, since the parameters of the rule used to be groups of states, the rule matching could not take place at the state level. With this werk, if you configure the state mapping for a single state the state mapping of all other states will be unaffected. CMK-12523 Change-Id: I0e7ae45a921193e266e4b248cf29f2d3f0cfb05a Compare: https://github.com/tribe29/checkmk/compare/94aea8136730...378d799ea46f