Werk #20143: Azure VM and database CPU utilization: configured thresholds now take effect
| Component | Checks & agents | ||||
| Title | Azure VM and database CPU utilization: configured thresholds now take effect | ||||
| Date | Jun 24, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
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.