Hi,
I’m currently looking at migration plan for several sites running on older rev of check_mk (1.2.x) to latest.
I know how to upgrade the sites, but I notice several monitored hosts within each site that have the older check_mk agent installed.
can I get away with upgrading the sites and still monitoring the hosts using older check_mk agent?
does the check_mk agent have to updated everytime check_mk server is updated (within the same major version) ? or is there backwards compatibility?
can someone point me to a doc that explains the (fastest/simplest/non-disruptive) way to update several hosts to the desired version of check_mk agent?
Yes - it can only be that some information is missing what is only provided by newer agents
As before agents can be older then the server.
Depends on the type of software distribution you are using for your servers.
If you use the enterprise edition you can also use the agent bakery and deployment.
So, even thought we now run CEE instead of raw, instead of doing the Agent Bakery style approach, we opted to use our existing CM mechanisms to push the changes out to our hosts. That may be a viable approach for people using raw.
For those who do not use the agent bakery: Remember to also check and, if necessary, update the agent plugins you have installed on your monitored hosts.
I’m running on raw and when it was just a few hosts that needed updating I did it manually, or just didn’t bother to upgrade the agent
But for now I have puppet in place to take care of the distribution of new agent versions. I just replace the check_mk_agent script on the puppet master and off it goes to all the clients. If you prefer nice GUIs to configure something like this you can also try rudder which will do the same for you. (And I bet there’s many more of these tools).
In puppet it’s very easy. Just distribute the check_mk_agent script (and plugins you use) to the right place. Somthing like this in your manifest should do the trick: