Hi,
in distributed monitoring, the remote site still need a Port 80/443 connection to the central site to get agent updates. SInce this is the only rule between remote TO central, wouldnt it be an improvement to use an existing connection like liveproxy? Or even better: central pushes baked clients to any remote, there the remotes kind of “cache” is and push it further to all agents (push update)? Aare there any ideas on that already?
Since Checkmk 2.0.0 it has also been possible to distribute baked agents via remote sites. The prerequisite for this is a setup with a central configuration and a connection which allows the central site to be reached from the remote sites via HTTP/HTTPS.
Yes, thats the current way we use it, but requires remote → central Port forwarding.
I opened a feature request for that (still in review).
Technically the livestatus API is for monitoring data and commands to the monitoring core.
The agent updates are distributed by the setup component which is something completely different and part of the web application. Hence the requirement for port 443 from remote to central site.
Yes, I know. But in future maybe CMK could get rid of this (or add some special handling (push)). In DMZ environments, opening connection from DMZ to internal network is a problem 
but currently required, if one want to use Auto-Updates.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.