If it were only one host and two tests, yes, this would be a simple and clear way to do this. However this config was only an example to demonstrate the bug - the real configuration is a lot longer. Doing it this way would end up with an incredibly large and unwieldy alerts.cfg.

This particular xymon installation has ~60 hosts and many hundreds of tests. The tests have different alert requirements but can basically be classified into four categories:

1. Call group A 24/7
2. Call group A 8/5
3. Call group B 24/7
4. Call group B 8/5

Different tests on the same machines belong to different alert groups. In addition, the different groups would like to have their own page where they can see just their own hosts/tests.

Listing all the tests in alerts.cfg would be madness (I know because that's how it's been done previously).

So this was my idea on how to solve this issue. Another way I see would be to use bogus hostnames and make entries like "server1.example.com-groupA" and "server1.example.com-groupB", but I think that's horrendously ugly. It's only one machine after all. And there is a benefit to being able to see all the tests on a single machine, in addition to the groupA/groupB pages.

Anyway, is this a bug in xymon? I guess it must be, since the manpages say nothing about this as far as I can tell.

Best regards, Davíð

On Thu, 12 Jun 2014 16:29:55 +0000 "Root, Paul T" <Paul.Root at CenturyLink.com> wrote:

Why go through all this? Why not:

HOST=testserver SERVICE=test1 $ALERT_TYPE_1

HOST=testserver SERVICE=test2 $ALERT_TYPE_2

Simple, clear, and effective.

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Davíð Steinn Geirsson Sent: Thursday, June 12, 2014 11:12 AM To: xymon at xymon.com Subject: [Xymon] PAGE match and group-only

Hi all,

Consider the following hosts.cfg:

page testpage1 Test page 1 group-only test1 0.0.0.0 testserver

page testpage2 Test page 2 group-only test2 0.0.0.0 testserver

page hostdefs Host definitions 10.100.252.1 testserver # prefer

And alerts.cfg:

PAGE=testpage1 COLOR=red DURATION>5 $ALERT_TYPE_1

PAGE=testpage2 COLOR=red DURATION>5 $ALERT_TYPE_2

I would expect xymon to alert with $ALERT_TYPE_1 when testserver.test1 goes red. What actually happens is that sometimes $ALERT_TYPE_2 gets triggered as well, even though test1 does not appear on the page testpage2.

Anyone has any ideas? I'm guessing this is a bug in xymon, just want to see if anyone has patches or a workaround.

-- Bestu kveðjur / Best regards Davíð Steinn Geirsson Basis ehf | Síðumúli 32 | (+354) 575-0400