[Xymon] Max uptime exceeded alerts (was Re: Xymon Digest, Vol 62, Issue 8)

[J.C. Cleaver]

On Thu, March 10, 2016 6:56 am, Richard Hamilton wrote:
> Look at the UP setting in analysis.cfg.  Mine:
> UP 30 90d HOST=crabapple
> UP 30 90d HOST=myeye
> UP 5 90d HOST=lapple
>
> 1st number is minimum uptime before the CPU column (may) go green (in
> minutes if no suffix) 2nd number is maximum uptime before it goes yellow.
> Those three are Macs; since AFAIK, they don't have ECC RAM, so longer
> uptimes would be pushing my luck, although they'd almost certainly need a
> reboot for an update or something before 90 days anyway.  For my Suns, the
> defaults (see below) seem more appropriate. :-)
>
> Defaults are said in the comments in analysis.cfg to be 1h (hour) and -1
> (infinite); but it has not worked for me to set for example 5 and -1.
>
> CPU might go yellow either from high load or from being outside the uptime
> boundaries.
>
> On Thu, Mar 10, 2016 at 8:34 AM, Agege Information Systems, Inc. <
> cs at agege.com> wrote:
>
>> Greetings,  Is there anyway to get an Xymon alert on Windows server that
>> has been running for over 120days.
>>
>> -Agege

As a side note, the '--uptime-status' option to xymond_client (assuming
server-side processing) can break this out into a separate column, in case
a distinction is wanted to be made in the CPU test between CPU issues and
the uptime flag.

I'll check on the '-1'... AFAIK, that should be valid as an "infinite"
value there.


Regards,
-jc