So you have 2 servers, and on one, you want all of the clients that send data to it, and on the second, you want just some.

It would be a lot of configuration, but, you could do this:

            Start the xymon proxy on port 1984.
            Start the xymon server on port 1985.
            Configure the proxy to send to localhost:1985 plus the remote server on 1984.

            Now configure the clients you want to go to both servers to send to port 1984, and the servers you just want on the local server to go to 1985.

            Or vice-versa, depending on which subset of clients would be smaller/less likely to change.

Paul.

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Jeremy Laidman Sent: Friday, November 04, 2016 3:31 PM To: Maik Heinelt; xymon at xymon.com Subject: Re: [Xymon] Xymon client data forwarding to another Xymon server?

Main

On Fri, 4 Nov 2016, 11:01 Maik Heinelt <maik at vegasystems.com<mailto:maik at vegasystems.com>> wrote: We have some clients behind a firewall what are sending their Xymon logs to a Xymon server at the same subnet. The Xymon server is the only one machine what is able to send the client data somewwere else, so we would like to get this server sending the local client data to another Xymon server, too.

Not all client data should be send, we would like to be able (if possible) to select the clients being send to the other server.

This is the difficulty - being selective. Perhaps you could send all client data but then just ignore the hosts you don't care about, or put them on a page that nobody looks at.

I was reading about xymonproxy, but it sounds, it only can send all client data to another server?!

Correct.

I wonder of it's practical to script up a kind of proxy. You could use the output of "$XYMON $XYMSRV xymondboard" to list all hosts that are tagged the way you want to select then (eg tag them with a NET parameter) and also list only those with client data.

Then with that list of hosts (or simply manage your own list in a text file), you grab the current client data with "$XYMON $XYMSRV clientlog" and send the output to "$XYMON $XYMSRV client" (with appropriate header).

Then sleep for 5 minutes and repeat.

Consideration should be given to detecting and suppressing stale client messages. Also, this technique may not be particularly efficient, so care should be taken if you have a lot of hosts to forward, and you may get bursts of high load on your intermediate xymon server. And there could be up to 5 minutes delay, unless you poll more often and limit the client data accordingly.

Also, there are almost no manuals or detailed information how to get xymonproxy setup.

Just the man page, but I think it's pretty good. Please ask any questions not answered by the man page.

Also, in the past there have been some discussions on this list about xymonproxy, so searching the archives might give done more hints.

J

It would be great to get some help to understand how to get it working.

Thank you in advance

Maik Heinelt

-- .................................................................. Heinelt Maik | Software Developer ハイネルト　マイク 愛知県一宮市富士２－２－２２ 株式会社 ベガシステムズ TEL: 0586-71-3903 FAX: 0586-71-4071 http://www.vegasystems.com Skype ID: daliose .................................................................. DISCLAIMER: This information is confidential and is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, please disregard and destroy this email and its content. Thank you

Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.