CheckMK cmcdump

Hello all,

I’m hoping someone can point me in the right direction. Up till now all of our remote customers in our MSP environment have been configured with livestatus configuration.

It was a matter of time but we have a new customer to onboard to our environment who can’t use the livestatus config due to restrictions on the firewall which can’t be bypassed.

So i setup an CMCDUMP config as described in Distributed monitoring - Scaling and distributing Checkmk

I’m generating the files locally on the customer sites, uploading it to a cloud storage and then download the files to our central site and this works quite easily. Wasn’t much of a problem to setup.

However i’m now running into the following, all the config that’s being imported in this way is getting imported in our own environment instead of a different customer. So all their monitored hosts and services show up in our own monitored items from our own environment.

I can’t seem to find an option or way to set these items to a different customer. Is there any way to separate these items into their own customer? I want to do this so that everyone here who uses checkmk here can see these items belong to customer X instead of guessing whether it’s something from our own environment or theirs. Or even worse when another customer with CMCDUMP get’s onboarded and it shows 3 different environments into 1 view.

1 Like

You might try the --prefix option to cmcdump. According to the --help, it will

add PREFIX to host names, useful for disambiguation in a multi-site setup

i.e. cmcdump --prefix customer-x …
The hostnames will then be prefixed with ‘customer-x’.

Beside the prefix option mentioned from @Dirk (that i strongly recommend to use) you need to restore the dump to it’s own site if you want to see it as a own customer.

1 Like

You can create a local “customer” site, as andreas mentioned, and import the data into that site. All imported data is read-only, i.e. you cannot set up any alerts etc. for these hosts and services.

1 Like

Hi All, thanks for the quick replies!

This was indeed what I was looking for. Using the --prefix option resolved it and made it clear for everyone what environment is being monitored.

Case resolved!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.