We have an ecosystem of a number of distributed monitoring servers which are consuming services from thousands of stores.
These stores will be at a mix of versions from 1.6, 2.1 and 2.2.
Is there a recommended way forward with this? Is there a way to discern the store version and connect it to a correct distributed monitoring server on the API request?
Also for 2.3 only to be BWC to 2.2 does seem quite close, particularly for our usecase.
The agent version is not the real problem - i have many systems with old agents where updates are not possible so easy and they work without problems with the current CMK server versions. The important version is the CMK server version. This version needs to be the same major version in your distributed environment.
Yes, so the version in the stores is <=2.1.
The distributed server that consumes the services from the many servers needs to be 2.3.
If this is your client version then this version can speak with an server version of 2.3. It can only happen that you need to update used plugin scripts. But you should also read the security fixes for the agents as it can be good to update agents if there is a security problem locally.
Updates and Upgrades doesn’t have 2.1 in the table at all; however we also must cater for 1.6 servers feeding into the distributed server.
As i said before it is important what version your CMK server has. The agent version on the monitored systems is not so important.
The linked article is also only about updating the CMK servers.
Sorry, maybe I’m not making myself clear. Nothing here is about the agents at all. Only about distributed monitoring.
I have many distributed monitoring servers that consume data via liveproxy for a number of servers each. This is server to server – absolutely no agents involved in any way, shape or form. As I said, maybe I’m not making myself clear.
Some of those servers feeding data to the main distributed servers are at 1.6. Some are at 2.1. The main distributed servers will soon be 2.2/2.3. However according to the article I posted that configuration won’t work.
Is there a patch we can apply to make it work or something we can do to get over this backwards compatibility hurdle? If not, then we’ll need to either run redundantly or modify CMK code ourselves, and consider our options going forward.
No
If you current setup is a real distributed setup with config push and so on then you need to have a servers at the same major version.
If you have only livestatus connection without config push then you can “patch” a little bit to have it working.