How to shorten delay before purple alerts? 🔗 link

wrote:

How can I change xymon to alert after a server has failed to report
for 15 minutes? We're finding that 30 minutes is too long a delay in
the production environment.

I see where you set purple delay for network tests and I see where you
can return it for individual tests, and I see where you can disable
purple. Is this a code change?

thanks Betsy

On Tue, Oct 11, 2011 at 12:42 AM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>wrote:

I finally had time to look around for this - it looks like the 30 minute
default is hard-wired into the code.

xymon-4.3.5/xymond/xymond.c, line 1210:


          int validity = 30;       /* validity is counted in minutes */

then at lines 1239-1241:

          if (strncmp(msg, "status+", 7) == 0) {
                validity = durationvalue(msg+7);
          }

So, an incoming message is given a validity of 30 minutes, unless set
otherwise by "status+X".

I just tested that by changing line 1210 to "validity=5", compiled,
installed, fired it up, sent a test status.  Five minutes later, I get a
purple dot for that test.

Ralph Mitchell


On Mon, Oct 3, 2011 at 9:35 AM, Elizabeth Schwartz <
user-c61747246f66@xymon.invalid> wrote:

How can I change xymon to alert after a server has failed to report
for 15 minutes? We're finding that 30 minutes is too long a delay in
the production environment.

I see where you set purple delay for network tests and I see where you
can return it for individual tests, and I see where you can disable
purple. Is this a code change?

thanks Betsy

<user-71895fb2e44c@xymon.invalid> wrote:

It would be really handy if this could be set by a variable within
xymonserver.cfg (eg XYMONDVALIDITY=30) and/or appending "--validity=N"
to
the command line in tasks.cfg.  Using the environment variable might be
preferable in some cases, because it can be used by other things link
xymonnet or custom test scripts.

On Tue, Oct 11, 2011 at 12:42 AM, Ralph Mitchell
<user-00a5e44c48c0@xymon.invalid>wrote:

I finally had time to look around for this - it looks like the 30
minute
default is hard-wired into the code.

xymon-4.3.5/xymond/xymond.c, line 1210:


          int validity = 30;       /* validity is counted in minutes */

then at lines 1239-1241:

          if (strncmp(msg, "status+", 7) == 0) {
                validity = durationvalue(msg+7);
          }

So, an incoming message is given a validity of 30 minutes, unless set
otherwise by "status+X".

I just tested that by changing line 1210 to "validity=5", compiled,
installed, fired it up, sent a test status.  Five minutes later, I get
a
purple dot for that test.

Ralph Mitchell


On Mon, Oct 3, 2011 at 9:35 AM, Elizabeth Schwartz <
user-c61747246f66@xymon.invalid> wrote:

How can I change xymon to alert after a server has failed to report
for 15 minutes? We're finding that 30 minutes is too long a delay in
the production environment.

I see where you set purple delay for network tests and I see where you
can return it for individual tests, and I see where you can disable
purple. Is this a code change?

thanks Betsy