Adding xymonproxy to the setup described earlier (Remote Site Monitoring With ssh-tunnel) allows for a more elegant configuration though …

How to connect a complete remote datacenter with ssh-tunnel and xymonproxy?

Combined with xymonproxy it is very easy to have a default-client configuration (i.e. no re-configuration of sshd). With only one ssh-tunnel a whole remote datacenter can be connected in a very resource friendly way by smoothing out spikes in the message stream to the xymon server with xymonproxy. Xymonproxy is included in the Xymon server package and is easy to configure.

For this to work

  • setup a ssh-tunnel on the server to establish a tunnel to xyproxy.remote.tld, make the remote port tcp/1985

  • setup xymonproxy on one machine xyproxy.remote.tld at the remote-datacenter and let it listen on the default-port tcp/1984 and report to localhost:1985

  • let all clients at the remote-location report to that proxy

See the project page and the include documentation for more details.