Xymon Mailing List Archive search

alerts includes

6 messages in this thread

list Galen Johnson · Thu, 19 Nov 2015 19:50:06 +0000 ·
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.  I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
     MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the last file listed in the alerts.d folder as the catchall.  I would never have noticed this had I not been having a test of some new servers using a script intended for another group.  Can anyone else confirm this behavior?  I'm currently using 4.3.21.

thanks

=G=
list Japheth Cleaver · Thu, 19 Nov 2015 12:46:59 -0800 ·
quoted from Galen Johnson
On Thu, November 19, 2015 11:50 am, Galen Johnson wrote:
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.
I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
     MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the
last file listed in the alerts.d folder as the catchall.  I would never
have noticed this had I not been having a test of some new servers using a
script intended for another group.  Can anyone else confirm this behavior?
 I'm currently using 4.3.21.

Is the line visible from xymond_alert --dump-config as such? After a
directory entry, it should simply continue on parsing from there in the
original file.


-jc
list Galen Johnson · Thu, 19 Nov 2015 22:55:23 +0000 ·
Yep.  It shows up.  It's really bizarre as I couldn't find anything that might trigger it but it stopped alerting to the wrong group as soon as I added a config file for that host group.

=G=
quoted from Japheth Cleaver

From: J.C. Cleaver <user-87556346d4af@xymon.invalid>
Sent: Thursday, November 19, 2015 3:46 PM
To: Galen Johnson
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

On Thu, November 19, 2015 11:50 am, Galen Johnson wrote:
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.
I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
     MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the
last file listed in the alerts.d folder as the catchall.  I would never
have noticed this had I not been having a test of some new servers using a
script intended for another group.  Can anyone else confirm this behavior?
 I'm currently using 4.3.21.

Is the line visible from xymond_alert --dump-config as such? After a
directory entry, it should simply continue on parsing from there in the
original file.


-jc
list Galen Johnson · Mon, 23 Nov 2015 14:45:29 +0000 ·
This is still bugging the hell out of me.  It's consistently sending to the wrong alert group.  I tried running

../bin/xymond_alert --test tbowl-midtier wksbasic --color=red


This seems to want to match on the wrong rule and I'm damned if I can see it.

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 137
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).*' ***

It does seem that it is matching on the correct rule also...

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 144
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(tbowl-).*' ***

Here are the 2 relevant rules:

137   HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).* 

  144   HOST=%(tbowl-).*

What am I missing?

=G=
quoted from Galen Johnson

From: Xymon <xymon-bounces at xymon.com> on behalf of Galen Johnson <user-87f955643e3d@xymon.invalid>
Sent: Thursday, November 19, 2015 5:55 PM
To: J.C. Cleaver
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

Yep.  It shows up.  It's really bizarre as I couldn't find anything that might trigger it but it stopped alerting to the wrong group as soon as I added a config file for that host group.

=G=

From: J.C. Cleaver <user-87556346d4af@xymon.invalid>
Sent: Thursday, November 19, 2015 3:46 PM
To: Galen Johnson
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

On Thu, November 19, 2015 11:50 am, Galen Johnson wrote:
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.
I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
     MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the
last file listed in the alerts.d folder as the catchall.  I would never
have noticed this had I not been having a test of some new servers using a
script intended for another group.  Can anyone else confirm this behavior?
 I'm currently using 4.3.21.

Is the line visible from xymond_alert --dump-config as such? After a
directory entry, it should simply continue on parsing from there in the
original file.


-jc
list Galen Johnson · Mon, 23 Nov 2015 15:56:26 +0000 ·
I just found the match...midtier matches "tier"...
quoted from Galen Johnson

=G=

From: Xymon <xymon-bounces at xymon.com> on behalf of Galen Johnson <user-87f955643e3d@xymon.invalid>
Sent: Monday, November 23, 2015 9:45 AM
To: J.C. Cleaver
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

This is still bugging the hell out of me.  It's consistently sending to the wrong alert group.  I tried running

../bin/xymond_alert --test tbowl-midtier wksbasic --color=red


This seems to want to match on the wrong rule and I'm damned if I can see it.

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 137
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).*' ***

It does seem that it is matching on the correct rule also...

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 144
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(tbowl-).*' ***

Here are the 2 relevant rules:

137   HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).*

  144   HOST=%(tbowl-).*

What am I missing?

=G=

From: Xymon <xymon-bounces at xymon.com> on behalf of Galen Johnson <user-87f955643e3d@xymon.invalid>
Sent: Thursday, November 19, 2015 5:55 PM
To: J.C. Cleaver
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

Yep.  It shows up.  It's really bizarre as I couldn't find anything that might trigger it but it stopped alerting to the wrong group as soon as I added a config file for that host group.

=G=

From: J.C. Cleaver <user-87556346d4af@xymon.invalid>
Sent: Thursday, November 19, 2015 3:46 PM
To: Galen Johnson
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

On Thu, November 19, 2015 11:50 am, Galen Johnson wrote:
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.
I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
     MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the
last file listed in the alerts.d folder as the catchall.  I would never
have noticed this had I not been having a test of some new servers using a
script intended for another group.  Can anyone else confirm this behavior?
 I'm currently using 4.3.21.

Is the line visible from xymond_alert --dump-config as such? After a
directory entry, it should simply continue on parsing from there in the
original file.


-jc
list Adam Goryachev · Mon, 23 Nov 2015 11:57:21 -0500 ·
Hi sorry sending from my mobile but see below 
Sent from my mobile
Adam Goryachev
quoted from Galen Johnson
On 23 Nov 2015, at 09:45, Galen Johnson <user-87f955643e3d@xymon.invalid> wrote:

This is still bugging the hell out of me.  It's consistently sending to the wrong alert group.  I tried running

../bin/xymond_alert --test tbowl-midtier wksbasic --color=red


This seems to want to match on the wrong rule and I'm damned if I can see it.

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 137
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).*' ***

It does seem that it is matching on the correct rule also...

00010238 2015-11-23 09:30:38 Matching host:service:dgroup:page 'tbowl-midtier:wksbasic:SAS Servers:TBowl' against rule line 144
00010238 2015-11-23 09:30:38 *** Match with 'HOST=%(tbowl-).*' ***

Here are the 2 relevant rules:

137   HOST=%(eu1[ed]|eucass[1-4]|dse|wsssl[6-7]|tier|eu-|wpentaho|wmysql).* 
This matches because you have |tier| in the host regex which matches tbowl-midTIER see capital part....

Hope that helps

Regards
Adam
quoted from Galen Johnson
 144   HOST=%(tbowl-).*

What am I missing?

=G=

From: Xymon <xymon-bounces at xymon.com> on behalf of Galen Johnson <user-87f955643e3d@xymon.invalid>
Sent: Thursday, November 19, 2015 5:55 PM
To: J.C. Cleaver
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes

Yep.  It shows up.  It's really bizarre as I couldn't find anything that might trigger it but it stopped alerting to the wrong group as soon as I added a config file for that host group.

=G=

From: J.C. Cleaver <user-87556346d4af@xymon.invalid>
Sent: Thursday, November 19, 2015 3:46 PM
To: Galen Johnson
Cc: xymon at xymon.com
Subject: Re: [Xymon] alerts includes
On Thu, November 19, 2015 11:50 am, Galen Johnson wrote:
Hey,


I seem to be having a weird issue I'm hoping someone else can confirm.
I'm us?ing "directory" to manage my alerts configs.


For example

directory /opt/xymon/server/etc/alerts.d

HOST=*
    MAIL user-3c7f3dc6228c@xymon.invalid DURATION>10 REPEAT=30 RECOVERED

However, it doesn't seem to actually get to the HOST entry.  It uses the
last file listed in the alerts.d folder as the catchall.  I would never
have noticed this had I not been having a test of some new servers using a
script intended for another group.  Can anyone else confirm this behavior?
I'm currently using 4.3.21.

Is the line visible from xymond_alert --dump-config as such? After a
directory entry, it should simply continue on parsing from there in the
original file.


-jc