Werk #20069: Check_MK service: Show cluster node name in agent status
| Component | Core & setup | ||||
| Title | Check_MK service: Show cluster node name in agent status | ||||
| Date | Jun 9, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
When monitoring a cluster host, the Check_MK service collects the agent (and
other data source) status of every cluster node. Previously each line only
showed the data source - for example [agent] Success, or when a node could
not be reached [agent] Communication failed: ...(!!). Because the node name
was missing, you could not tell which node an entry belonged to: when one
node's agent timed out or was unreachable, the Check_MK service went CRIT
without revealing the culprit, and you had to look up the cluster's nodes and
inspect each one individually.
The Check_MK service now appends the node name to each per-node line on
cluster hosts. A failing node is immediately visible, e.g.
[agent] Communication failed: [Errno 113] No route to host on node node03(!!),
and healthy nodes are no longer indistinguishable:
[agent] Success on node node01, [agent] Success on node node02.
This only affects cluster hosts; the output for regular (non-cluster) hosts is unchanged.