20143 FIX Azure VM and database CPU utilization: configured thresholds now take effect

The warning and critical levels configured for the following services of the
current Azure integration (`azure_v2`) had no effect and the services kept
using their built-in default levels:

* **Azure/VM CPU Utilization**
* **Azure/DB for PostgreSQL CPU**
* **Azure/DB for MySQL CPU**

The checks now use the correct params key.

SUP-29577

Change-Id: I230483bfe0ddf88baff82682d047287c8f0938a9

Author: DavidGerva

.werks/20143.md

@@ -0,0 +1,38 @@
+[//]: # (werk v3)
+# Azure VM and database CPU utilization: configured thresholds now take effect
+
+key        | value
+---------- | ---
+date       | 2026-06-24T15:21:41.397087+00:00
+version    | 2.5.0p8
+class      | fix
+edition    | community
+component  | checks
+level      | 1
+compatible | no
+
+The warning and critical levels configured for the following services of the
+current Azure integration (`azure_v2`) had no effect; the services always used
+their built-in default levels:
+
+- Azure/VM CPU Utilization
+- Azure/DB for PostgreSQL CPU
+- Azure/DB for MySQL CPU
+
+The check plugins read the levels from the wrong parameter key, so the
+thresholds configured via the _CPU utilization (single value)_ rule (previously
+_CPU utilization for appliances_) were silently ignored.
+
+The check plugins now read the levels from the correct key, so this rule takes
+effect for the affected services.
+
+Advisory: if you have already configured the _CPU utilization (single value)_
+rule for hosts running these services, the levels now apply on the next check
+cycle. Review the rule (and the affected services) after
+updating if you want to avoid unexpected state changes.
+
+Additionally, the check manuals for these services previously referred to the
+wrong rule, _CPU utilization_ (the per-item variant), which these services
+cannot use. If you created that rule expecting it to configure these services,
+it never took effect and is now orphaned. Remove it and configure the levels
+with the _CPU utilization (single value)_ rule instead.

cmk/plugins/azure_v2/agent_based/azure_mysql.py

@@ -70,7 +70,7 @@ def check_azure_mysql_memory(
     ),
     check_function=check_cpu(),
     check_ruleset_name="cpu_utilization",
-    check_default_parameters={"levels": (65.0, 90.0)},
+    check_default_parameters={"util": (65.0, 90.0)},
 )
 
 

cmk/plugins/azure_v2/agent_based/azure_postgresql.py

@@ -75,7 +75,7 @@ def check_azure_postgresql_memory(
     ),
     check_function=check_cpu(),
     check_ruleset_name="cpu_utilization",
-    check_default_parameters={"levels": (65.0, 90.0)},
+    check_default_parameters={"util": (65.0, 90.0)},
 )
 
 

cmk/plugins/azure_v2/agent_based/azure_virtual_machine.py

@@ -155,7 +155,7 @@ def check_azure_vm_cpu_utilization(
                 "util",
                 "CPU utilization",
                 render.percent,
-                upper_levels_param="levels",
+                upper_levels_param="util",
             )
         ]
     )(params, section)
@@ -168,7 +168,7 @@ def check_azure_vm_cpu_utilization(
     discovery_function=discover_azure_vm_cpu_utilization,
     check_function=check_azure_vm_cpu_utilization,
     check_ruleset_name="cpu_utilization",
-    check_default_parameters={"levels": (65.0, 90.0)},
+    check_default_parameters={"util": (65.0, 90.0)},
 )
 
 

cmk/plugins/azure_v2/agent_based/lib.py

@@ -462,7 +462,7 @@ def check_cpu() -> CheckFunctionWithoutItem:
                 "util",
                 "CPU utilization",
                 render.percent,
-                upper_levels_param="levels",
+                upper_levels_param="util",
             )
         ]
     )

cmk/plugins/azure_v2/checkman/azure_v2_mysql_cpu

@@ -5,7 +5,7 @@ license: GPLv2
 distribution: check_mk
 description:
  This check reports the cpu utilization in percent.
- You can configure levels using the rule "CPU Utilization".
+ You can configure levels using the rule "CPU utilization (single value)".
 
 discovery:
  One service is created for each database if the required metric

cmk/plugins/azure_v2/checkman/azure_v2_postgresql_cpu

@@ -5,7 +5,7 @@ license: GPLv2
 distribution: check_mk
 description:
  This check reports the cpu utilization in percent.
- You can configure levels using the rule "CPU Utilization".
+ You can configure levels using the rule "CPU utilization (single value)".
 
 discovery:
  One service is created for each database if the required metric

cmk/plugins/azure_v2/checkman/azure_v2_vm_cpu_utilization

@@ -7,7 +7,7 @@ description:
  This check provides information about VM CPU utilization in
  the Microsoft Azure cloud.
 
- The thresholds can be configured using the rule "CPU Utilization".
+ The thresholds can be configured using the rule "CPU utilization (single value)".
 
 discovery:
  One service is created on every VM host. The option

tests/unit/cmk/plugins/azure_v2/agent_based/test_azure.py

@@ -946,7 +946,7 @@ def test_check_memory(
         (
             PARSED_RESOURCE,
             "checkmk-mysql-server",
-            {"levels": (0.0, 0.0)},
+            {"util": (0.0, 0.0)},
             [
                 Result(state=State.CRIT, summary="CPU utilization: 0% (warn/crit at 0%/0%)"),
                 Metric("util", 0.0, levels=(0.0, 0.0)),

tests/unit/cmk/plugins/azure_v2/agent_based/test_azure_mysql.py

@@ -454,7 +454,7 @@ def test_check_network(
                     ),
                 },
             ),
-            {"levels": (80.0, 90.0)},
+            {"util": (80.0, 90.0)},
             [
                 Result(state=State.OK, summary="CPU utilization: 50.00%"),
                 Metric("util", 50.0, levels=(80.0, 90.0)),
@@ -477,7 +477,7 @@ def test_check_network(
                     ),
                 },
             ),
-            {"levels": (80.0, 90.0)},
+            {"util": (80.0, 90.0)},
             [
                 Result(
                     state=State.CRIT,