CheckMK distributed Monitoring with centralized configuration - Make slave standalone

Hi guys,

we are using CRE 2.0.0p21 distributed Monitoring and some connected slave sites with centralized configuration.

In this article it is described how to connect standalone CheckMK sites to distributed Monitoring and centralized configuration:

But now we have the opposite case that we need to disconnect one slave site and make this site standalone.

How can we disconnect one slave site, make it standalone, and keep the configuration (hosts) for this site? What would be the best practice how to?

Best regards

Tobias

Hi,
if you use CRE or CEE for distributed monitoring, then the entire configuration of the central site is automatically transferred to the remote site. You should have the configuration on the remote site.

Karl

Hi Karl,

alright. That means the following steps should work:

Activate Wato Config on the slave site if this was disabled from the master
Login to the slave site and create a new cmkadmin
Disable Livestatus with omd config
Disable or delete the slave site on the master in the distributed monitoring section
Site should be useable standalone

I am going to try this in 2 months. I can keep you posted if this works.

Regards
Tobias

The order was not correct, this is the right order:

Activate Wato Config on the slave site if this was disabled from the master
Disable Livestatus with omd config
Login to the slave site and create a new cmkadmin
Disable or delete the slave site on the master in the distributed monitoring section
Site should be useable standalone
Keep in mind that on the site are still all users and hosts from the main site which may be deleted manually then