We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Checkmk 1.6 has arrived! Learn more about it here!

Werk #7250: Check_MK Discovery: Clusters were unable to automatically discover new services

ComponentChecks & Agents
TitleCheck_MK Discovery: Clusters were unable to automatically discover new services
Date2019-03-22 09:36:39
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.6.0b1
LevelTrivial Change
ClassBug Fix
CompatibilityIncompatible - Manual interaction might be required

The Check_MK Discovery check for a cluster was able to identify new/vanished services. However, the automatic discovery mechanism in the background failed to integrate them into the configuration.

This has been fixed. There is still some constraint which makes this werk incompatible. The Periodic service discovery rule allows you to configure Automatcally activate changes for the specified host. If you want automatic activation of new services for cluster hosts, you have to configured a rule on the nodes instead of the cluster hosts. So any Periodic service discovery rules of clusters should be duplicated onto the nodes.

This requirement is currently necessary because of the internal configuration. Clusters never have an explicit configuration file, the actual clusters configuration is compute on demand.