Werk #22074: Azure v2: Resource Health service no longer flaps when Azure reports no health status
| Component | Checks & agents | ||||
| Title | Azure v2: Resource Health service no longer flaps when Azure reports no health status | ||||
| Date | Aug 4, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
This affects users monitoring Azure with the azure_v2 special agent.
The "Check_MK" service of those hosts intermittently went to WARN with
Missing monitoring data for plugins: azure_v2_resource_health
and the "Azure/Resource Health" service went stale, only to recover on one of the following check cycles.
This happened because the Resource Health API omits resources with no health data,
for example for deallocated virtual machines. Azure does this intermittently, so the
azure_v2_resource_health section appeared and disappeared from run to run.
The special agent now always emits a section for every monitored resource. If Azure returned no health status for a resource, the agent writes an explicit placeholder with the availability state "Unknown", and the check plugin reports it as OK with the summary
No health status returned by the Azure Resource Health API
Resources for which Azure does report a health status are unaffected: a state other than "Available" still makes the service CRIT, unless the reason type is "Customer Initiated".
Please note that resources which Azure never reports a health status for, now get an "Azure/Resource Health" service on their next service discovery. For this reason this werk is flagged as incompatible. These services are OK and carry the summary quoted above.