[Xymon] routing between xymons

[Robert Schetterer]

Am 13.05.2016 um 17:13 schrieb Ron Cohen:
> Hello there...
> we have here a pretty big production environments, and even bigger
> non-production. 
> I've configured xymon for both, but the guys that do the actual
> monitoring objected to have alerts coming from non-production servers,
> since those are mostly non-crucial - they don't want to see any of those
> reds on their screens.

why not

NOCOLUMNS:column[,column]

for testing stuff

https://www.xymon.com/help/manpages/man5/hosts.cfg.5.html

NOCOLUMNS:column[,column]
    Used to drop certain of the status columns generated by the Xymon
client. column is one of cpu, disk, files, memory, msgs, ports, procs.
This setting stops these columns from being updated for the host. Note:
If the columns already exist, you must use the xymon(1) utility to drop
them, or they will go purple.



> I played for some time with the alert propagating, but  it won't do, so
> sadly I disabled all the non-prod clients.
> The obvious solution (unless there's a simpler one) is to start another
> xymon on different port and different URL. the problem is that it
> requires a firewall setting, which is a major headache to make.
> what i thought of, is to do routing at the bb port, so incoming clients
> will be routed according to the IP origin to the prod and non-prod
> xymond (say ports 1985 & 1986).
> It is not difficult to implement,  but before pythonizing it, i wonder
> if there is an existing solution within xymon which i missed, or anyone
> else already done it?
> many thanks
> _rony
>  
> 
> 
> 
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
> 



Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein