Would it be possible to add a default group label for each line automatically in the client configuration so you don't have to qualify them on every entry? It doesn't really matter what label name is used. It would make it easier to configure the alerts since all rules would have a group associated and you won't get excessive notifications on items that don't have a group label.
Jason
I didn't get a response last week so I'll explain the issue.
If you set a local test without a GROUP label it will cause all alerts that match to fire, regardless of whether they have a GROUP label or not.
To use the GROUP functionality properly every test that requires a different group will require a label for every entry for a host/service, depending on how you've configured your hobbit-alerts.cfg I would like the default to be to send a GROUP label with every set of tests and have the hobbit-alerts.cfg to have a default group for matching when no group is assigned.
Looking at the code it doesn't seem like it'd be too hard to add. Add a default in getalertgroups() for the client, maybe after the processing of the line in load_alertconfig() (line 653 from the 7/12 snapshot) for the server.
Let me know what you think.
Jason
From: Kruse, Jason K. Sent: Monday, July 10, 2006 9:51 AM To: 'hobbit at hswn.dk' Subject: Default groupings
Would it be possible to add a default group label for each line automatically in the client configuration so you don't have to qualify them on every entry? It doesn't really matter what label name is used. It would make it easier to configure the alerts since all rules would have a group associated and you won't get excessive notifications on items that don't have a group label.
Jason
Hi Jason,
On Thu, Jul 20, 2006 at 10:15:40AM -0500, Kruse, Jason K. wrote:
If you set a local test without a GROUP label it will cause all alerts that match to fire, regardless of whether they have a GROUP label or not.
To use the GROUP functionality properly every test that requires a different group will require a label for every entry for a host/service, depending on how you've configured your hobbit-alerts.cfg I would like the default to be to send a GROUP label with every set of tests and have the hobbit-alerts.cfg to have a default group for matching when no group is assigned.
If I understand you correctly, you have a setup like this. In hobbit-clients.cfg you tag some e.g. disk statuses with a group label, and some do not have a group label:
HOST server1
DISK / 80 90 groupid=admins
HOST server2
DISK / 85 95And in hobbit-alerts.cfg you then have the "admins" group alerts going to one recipient and the other alerts going to someone else:
SERVICE=disk GROUP=admins
MAIL admins at foo.com
SERVICE=disk
MAIL someone at foo.comI think the real problem is different - when you have a test that does not have any GROUP association, then alert rules with a specific GROUP label should not be matched. And the current code doesn't behave quite as it should; there's a patch attached to this mail. So with that patch let me walk through how I think it should work.
If server1 gets a disk alert, it will be tagged with the "admins" group label. This will currently match both of the alert rules; the first one obviously because the group label matches, and the second one because it doesn't have any group filter at all. This doesn't seem right - and it's the problem you describe. I think the best solution here is to change the last alert rule to
SERVICE=DISK EXGROUP=*
MAIL someone at foo.comso it is clear that this rule is not used whenever the status is tagged with a group label. Does that sound like a reasonable solution?
If server2 gets a disk alert, it won't have any group label. So it won't match the first alert rule (group doesn't match), and it will match the second one - both in the form with and without the EXGROUP setting. So that behaves as one would expect.
Regards, Henrik
participants (2)
-
henrik＠hswn.dk
-
jason.kruse＠teldta.com