Two days ago, we upgraded to Checkmk 2.4. The distributed piggyback mechanism was one the most anticipated features, and we activated it right away. Now, two days later, suddenly those hosts that benefit from this mechanism (VMs that are monitored on a different Checkmk server than their vCenter Servers) suddenly show the expected services (“ESX …”) as newly discovered, i.e. “Check_MK Discovery” is in state “WARN”.
Up to now I had the impression, that new services that require a service discovery are shown relatively fast, including a warning for Check_MK Discovery. Did it take the piggyback mechanism two days to pass the data around? Or is it just the warning that took two days to change to WARN? Unfortunately, I don’t have a time machine to go back to check…