Support multiple MKP versions in distributed monitoring

26 votes

We have a large distributed monitoring. An upgrade of this global environment take weeks or months. One challenge is, that currently MKPs are made available globally, regardless if the local site Checkmk version can run the MKP or not. There is no way to define if an MKP is for a specific version only

Released Suggested by: Thomas Lippert (26 Apr, '22) • Upvoted: 18 Oct, '22 • Comments: 4

Comments: 4

16 May, '22
Mike1098
The situation is that we have to run the distributed environment for a limited amount of time with master in prior version and some sites already updated to current version. Especially for upgrading from 1.6 to 2.0 the problem is that cluster aware and some SNMP based checks are not compatible between both versions which would force us to do the upgrade in one shot. In case there are undetected issues in the new versions we would have immediately this issues on ALL sites, even on our critical ones.
The new function should allow to install on master separate MPK´s for version 1. 6 and 2.0. With activation only the version which match the checkmk version of the remote site is activated.
20 May, '22
Heiko
Good idea and helpfull for slow WAN connections
24 Nov, '22
Mike1098
Thats implemented in 2.0.0p30
Thank you Tribe29, well done.
15 May, '23
Thomas Lippert Admin
Will be shipped in Checkmk 2.2.0. Moved to done, so I can share the plans for Checkmk 2.3.0 by marking the respective tickets