Werk #15246: Stale services on cluster nodes when the cluster is excluded from monitoring

Component

Checks & agents

Title

Stale services on cluster nodes when the cluster is excluded from monitoring

Date

Mar 17, 2023

Level

Trivial Change

Class

Bug Fix

Compatibility

Compatible - no manual interaction needed

Checkmk versions & editions

2.3.0b1 Not yet released	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk Cloud (CCE), Checkmk MSP (CME)
2.3.0b1	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk Cloud (CCE), Checkmk MSP (CME)
2.2.0b1	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk Cloud (CCE), Checkmk MSP (CME)
2.1.0p25	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
2.0.0p35	Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

If a cluster is excluded from the active monitoring, stale services would appear on its nodes under certain conditions.

A cluster (just as any other host) can be excluded from the active monitoring be either configuring a new rule "Hosts to be monitored", or by making the shipped default rule match the host by setting its tag "Criticality" to "Do not monitor this host".

If this is done in conjunction with the services being clustered using the ruleset "Clustered services for overlapping clusters", the Check_MK service and some of the passive services would go stale. This affected all services after the clustered services, sorted alphabetically according to their description.

To the list of all Werks