Implement a feature to leverage piggyback data, which are shared by a product integrated way from remote sites
we use rsync and cron to share the piggyback data between remote sites right now. Even if this works for us, it would be better to select which data should be shared to which remote site. In our case we have multiple remote sites and we don't need to share all piggyback data with all remote sites. So if you consider this feature, please provide a way to limit/select the shared piggyback data.
I'm missing a point in this discussion:Which piggyback data (maybe filtered for hosts somehow) of which site(s) is needed at which other site(s)?* maybe filtered data of remote1 is needed at central site* other/different filtered data from remote1 (attention: same site with other filters) is needed at remote2* some filtered data from central is needed at remote1 and remote2 (for whichever reason)* etc. etc.Just my 2ct.
We solved this for us using two custom endpoints in the REST API.One endpoint serves as the receiver and the other as the query interface for the Piggyback data.So it is possible to let the master of a distributed setup send piggyback data to the satellites. This is currently triggered by a cronjob in our setup.If needed, I can also provide this code.
Code would help, is it on the exchange or github Tim?
@Tim, sounds good. Would you please provide this?
I basically know no bigger Checkmk Installation (and I know quite some of them) who not have the Problem with Synchronization of Piggyback data. I saw rsync and even NFS solutions for that. All are hideous, but solve a problem what should not be a problem out of the box. The Problem starts if you have thousands of hosts, and want to have the Piggyback Information from e.g. your vCenter. As soon you can't scale them anymore on one site, and on Checkmk Servers on Virtual, that happens soon, you miss the information. The Same Problem goes for Veaam Backup, to name just two examples :). So, I really hope this will at some point a native checkmk feature.
HI guys! I recently asked for this on forum.https://forum.checkmk.com/t/piggyback-across-cmk-instances/37959Yes, please, it would be beautiful to have this... out of the box.
Upvote - Piggyback is a very powerful tool and Tribe should really look into pushing this capability even further. All mentioned comments are valid and i do not want to add too much. Only this: If Tribe were to bring this functionality to enterprise grade capabilities, Checkmk would have another key selling proposition at hand. For us, a less hiedous solution than our "own" solution would be a blessing.
Hello,Thank you for your idea. After thorough internal discussion, we’ve decided to plan its implementation for one of the next releases of our software.We look forward to keeping you updated on progress.At Checkmk we work on ideas based on business needs, customer demand, and resource availability. For strategic reasons, we reserve the right to re-evaluate the priority and/or scope of this feature as new information becomes available. We therefore ask for your understanding that we do not guarantee its implementation.Warm regards,Your Checkmk team
This feedback board is powered by Feature Upvote.
When submitting your email with a suggestion or comment, Feature Upvote uses your email to
Your email is never displayed to other users. Checkmk staff will be able to see your email address.
Feature Upvote's Acceptable Use Policy can be summarized as:
Read the full Acceptable Use Policy (in English)
We’ll email you when the status of the suggestion changes. You can unsubscribe at any time with a single click.