It happened again, we push the newest agent using our RMM tool, and once again the “service name” for the checkmk agent is new, so we end up having to do a TON of fixes exchanging the OLD service with NEW one in cmk discovery.
Why change the service name? This seems to just create extra work when we do upgrades. There’s enough to do already with plugin changes, and other modifications to the “names” of various services returns from other updates…
We’re running distributed monitoring with CMK raw.
Our RMM tool detects installed CMK agent versions and downloads/upgrades the CMK agent and some select plugins for us.
You can always let Checkmk use the “old” name, there are rules for that.
How did you manage to run the RAW edition with distributed monitoring? Isn’t that an Enterprise feature?
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.