Migrate remote Site into central Setup

General
1

According to Distributed monitoring - Scaling and distributing Checkmk (2.5) it is possible to migrate the folder structure from a remote site into the central Setup, to use distributed monitoring with “push configuration”.

I did test the migration on a playground but since we plan to move a lot of remote Sites into a few central Sites, I am still asking me two questions, that were hard to test:

  • Is there a way to migrate credentials (for example from a smb share check rule)
  • Do the agents installed on remote systems (without registration) need any after care?
  • Are there any things we should keep in mind (best practices), that are not yet documented under 2.5?
  • Anything else?

We are running CMK Ultimate MT 2.5

Thanks!

2

TBH: I am currently removing this section from the User Guide, since moving the host configuration is a very hacky approach that does not take into account hosts that have been renamed and hosts with conflicting names.

I’d rather suggest reading out host information via Livestatus and the REST-API and then either directly creating these hosts via REST-API or creating CSV lists to import later from the data. Regarding the agent packages: Fine, when you are not using the Agent Bakery. When using the Agent Bakery, at some point you have to tell the hosts to switch to the new Bakery.

There might also be glitches with Logwatch during the overlap period where the monitoring agent is queried by both Checkmk sites.

3

Okay interesting, thanks for your reply. Would be great to see a well documented way to achieve this “migration” in the fututre.

While testing I was dealing too with conflicting names etc but for the final migration I planned to check each host name so that it is individual. Besides that, the “hacky approach” did work really well while testing. But yeah, I guess I will maybe need to figure out a way to do it with REST.