Hi,
I noticed that a disable message is not setting the RECOVERY option to 1 when triggering an alert script.
From xymonserver.cfg: OKCOLORS="green,blue,clear"
And I also noticed that if you select multiple hosts and multiple services, only for 1 host the alert script is triggered for each service. Selecting 1 server or 1 service is working fine.
Stef
On Mon, January 25, 2016 12:27 am, Stef Coene wrote:
Hi,
I noticed that a disable message is not setting the RECOVERY option to 1 when triggering an alert script. From xymonserver.cfg: OKCOLORS="green,blue,clear"
Hi,
Various types of "recoveries" actually have different numeric values there. In 4.3.x, a disabling a test will set RECOVERED=2: https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.3.24/xymond/do_ale...
In 4.4, this will extend to values for stale and dropped alerts as well: https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.x-master/xymond/do...
To test whether a call out to a script is an alert or a recovery, it's best to check for 0 and non-0.
And I also noticed that if you select multiple hosts and multiple services, only for 1 host the alert script is triggered for each service. Selecting 1 server or 1 service is working fine.
Hmm. This is on the standard enadis.sh page? What is fired on the remaining hosts?
-jc
On Monday 25 January 2016 08:08:39 you wrote:
Hi,
Various types of "recoveries" actually have different numeric values there. In 4.3.x, a disabling a test will set RECOVERED=2: https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.3.24/xymond/do_ale rt.c#l580
In 4.4, this will extend to values for stale and dropped alerts as well: https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.x-master/xymond/do _alert.c#l594
To test whether a call out to a script is an alert or a recovery, it's best to check for 0 and non-0. Ok, I will update our alert script.
And I also noticed that if you select multiple hosts and multiple services, only for 1 host the alert script is triggered for each service. Selecting 1 server or 1 service is working fine.
Hmm. This is on the standard enadis.sh page? What is fired on the remaining hosts? Mhh, I don't get it. Now it's working like expected. I noticed it can take a few seconds to update all possible combinations. I tested it on a rather busy system and maybe I missed all the updates....
Stef
participants (2)
-
cleaver＠terabithia.org
-
stef.coene＠docum.org