[Xymon] Hello Everyone

[John Alexander]

xymonproxy is another option in cases like that.  I've used it where 
servers were not allowed to communicate directly out of a restricted 
network.

On 3/18/2019 08:38, John Thurston wrote:
>
> On 3/17/2019 9:37 PM, Matthew Gregory wrote:
>> Thanks for your reply, I am Debian on a non virtualized Server, and 
>> don’t have VPN do you know of any other way?Assuming that you have a 
>> VPN to your Azure and AWS environments, have the agents report back 
>> directly to your Xymon server.
>
> If you have a remote client which can not communicate directly back to 
> your xymon server, one can 'pull' the data from the host with the 
> server. This is not "basic" xymon. It isn't "expert" level, but I'd at 
> least put it at "advanced".
>
> To do something similar, I run a xymon client and 'msgcache' on the 
> remote host. The client reports to the cache on its own hostname. I 
> then have that host defined in my xymon server with a 'pulldata' tag. 
> The xymon server makes a connection to the remote host and retrieves 
> the cached messages.
>
>
>
> https://xymon.com/help/manpages/man8/msgcache.8.html
>
> https://xymon.com/help/manpages/man5/hosts.cfg.5.html
>
>> pulldata[=[IP][:port]]
>>     This option is recognized by the xymonfetch(8) utility, and 
>> causes it to poll the host for client data. The optional IP-address 
>> and port-number can be used if the client-side msgcache(8) daemon is 
>> listening on a non-standard IP-address or port-number. 
>
>
>
> -- 
>    Do things because you should, not just because you can.
>
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon