Checkmk Activation changes

We are planning to migrate from Checkmk 1.5 to Checkmk 2.4. Overall, everything looks good, but we came across one issue that has left me and my team a bit confused.

In the above images, the first one is from Checkmk 1.5 and the second (green one) is from Checkmk 2.4.

We have configured distributed monitoring in both versions. However, while configuring the LDAP connection in Checkmk 2.4, we noticed a difference. In version 1.5, whenever changes are made, they are reflected as 2 changes (1 for the primary site and 1 for the slave site). But in version 2.4, the same changes appear as only 1 change.

This leaves us uncertain whether the changes in version 2.4 are being applied to both sites or only to one.

Request someone from the community to please clarify this?

here is the other screenshot

Hi Chandra,

there are some config changes, that do not require a config reload (or activation of changes in the GUI) on the local site.
The LDAP Connector is one of those.

You need to activate the change for the remote site though, because the changes to the config will only get synced to your remote site on activation.

So technically in this case it is more “Sync Changes” rather than “Activate Changes” and it works as intended.

Hope that clears things up.

Cheers Jeronimo

Perfect

Thank you Jeronimo

Hello!

If one of the answers helped you solve your question, please mark it as the solution. This way, you thank the person who helped you and also indicate that the question has been resolved. This, in turn, helps others who come across the same question.

Solution

Thank you!