Good evening everybody,
writing here because there seems to be no satisfactory info everywhere else online.
I am in the middle of something not supported: Downgrading my customer’s configuration from a Managed Services installation to a Pro installation.
This is a very complex configuration with thousands of hosts, custom rules, thresholds, Oracle and Vcenters integrations…
Has anyone ever attempted this? I got suggested to use the APIs building my own scripts, and I was wondering if anyone has content to take inspiration from.
Thanks!
Pietro
1 Like
That might not be simple but from my perspective one good approach would be to classify the types of devices that you have and create a phased deployment, covering all hosts and rules per type (vSphere, Databases, Windows, Linux, etc). If your customer has majority of rules and hosts from your environment, then you can start with a backup and remove all the extra configurations that are not needed.
The “only” problem inside the manged service version is the customer attribute.
It should be possible to take the whole “~/etc/check_mk/” folder from you current installation and clean the customer attribute with some awk/sed magic.
The testing is then easy - take this cleaned config folder and try to edit the configuration with an test site.
4 Likes
Thanks Andreas, but I don’t think that would produce a supported configuration… I will see if someone comes up with another answer, maybe API related, and see how to proceed.
Thanks for now
1 Like
What do you mean with supported configuration?
If there is no customer attribute existing in your config and the “cmk --debug -vvU” don’t produce any error + a “cmk-update-config -vvv” also produce no problem it would think the configuration is ok.
For the API approach you have the problem that not really all settings are available as API endpoints.