Support PiggyBack data from remote hosts

Comments: 16     Oldest | Newest | Most likes | Fewest likes

• 04 May, '22
  Steffen Mueller

  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.

  Like 2
• 09 Jun, '22
  Marsellus Wallace

  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.

  Like
• 30 Jun, '22
  Tim

  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.

  Like 1
• 18 Oct, '22
  Stefan Baas

  Code would help, is it on the exchange or github Tim?

  Like
• 09 Jan, '23
  Doc

  @Tim, sounds good. Would you please provide this?

  Like
• 15 Mar, '23
  Bastian Kuhn

  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.

  Like 4
• 31 Mar, '23
  Jerry

  HI guys! I recently asked for this on forum.
  https://forum.checkmk.com/t/piggyback-across-cmk-instances/37959
  
  Yes, please, it would be beautiful to have this... out of the box.

  Like
• 14 Apr, '23
  Hambrock, I.

  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.

  Like 1
• 30 Nov, '23
  Niklas Pulina Admin

  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

  Like 7
• 19 Mar, '24
  Mohamed Saleh Admin

  Hello,
  
  Good news: We have started the development process.
  
  So what’s next? Depending on the scope of your idea, this process may include various steps such as detailed requirements research or a specification phase before it is passed on to development. During this process we may contact you for further information.
  
  Warm regards,
  Your Checkmk team

  Like 6
• 16 Jul, '24
  Lee Rumble

  Consider the following to please:
  
  A special agent which retrieve piggy back data. In distributed monitoring, you have the option to send plugins and agents in /local to remote sites. So that functionality allows you to have the special agent get the piggyback data on the remote site. But AWS agents for example dont have a Site option, so if you configure that agent from your primary CMK server, it will run there. If you provide the agents with the option of 'site' it should run on that site.
  
  Hope this helps and is coming soon!

  Like
• 16 Jul, '24
  Niklas Pulina Admin

  Hi Lee, thank you for your comment.
  
  A special agent will always run at the very site where the corresponding host is monitored. So if the AWS host is set up at a remote site, its special agent will run there (not at your central site) and can create piggyback data. In the future, you should be able to distribute this piggyback data to other sites.

  Like
• 29 Aug, '24
  Julien C.

  Hello,
  Good news that this functionality is in development.
  Do we have a rough idea on when it will be implemented in new releases ?
  Thank you.

  Like
• 30 Aug, '24
  Niklas Pulina Admin

  Hi Julien,
  
  The new "Distributed Piggyback" functionality will be released with Checkmk 2.4.
  
  Best, Niklas

  Like 2
• 06 Dec, '24
  Martin Hirschvogel Admin

  Hello,
  
  Good news! Your idea has been implemented into our software. The functionality is available upstream and will be published with Checkmk 2.4.
  
  Warm regards,
  
  Your Checkmk team

  Like 6
• 08 May
  Martin Hirschvogel Admin

  Hello,
  
  This feature is released with Checkmk version 2.4.0.
  See: https://checkmk.com/werk/17202
  
  Warm regards,
  
  Your Checkmk team

  Like 4