Xymon Mailing List Archive search

EXTIME/TIME syntax

5 messages in this thread

list Lynn Osburn · Thu, 7 Jun 2018 15:12:22 +0000 ·
Attempting to prevent "false" cpu alarms during overnight processing, I have included a line in analysis.cfg thus:
    LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400

However, alarms continue to be generated during the "excluded" hours.

Has anyone else had any difficulty with either TIME or EXTIME entries?

Thanks!
list John Thurston · Thu, 7 Jun 2018 08:08:47 -0800 ·
I use EXTIME in my alerts.cfg (v4.3.28), but I use numeric values for days of the week and have never tried using the 'W' value.

Does your test work if you define it as:
  12345:2200:0400


What version of Xymon are you using. Back in 2015, there was list-discussion of extime not working in 4.3.27
--
    Do things because you should, not just because you can.

John Thurston    XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
quoted from Lynn Osburn

On 6/7/2018 7:12 AM, Lynn Osburn wrote:
Attempting to prevent “false” cpu alarms during overnight processing, I have included a line in analysis.cfg thus:

     LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400

However, alarms continue to be generated during the “excluded” hours.

Has anyone else had any difficulty with either TIME or EXTIME entries?

Thanks!


N �n�r����)em�h�yhiם�w^��
list James Louis · Thu, 7 Jun 2018 11:53:06 -0500 ·
Lynn,

I've not seen an EXTIME but TIME conforms to the NKTIMES formatting listed
in hosts.cfg:

NKTIME=day:starttime:endtime[,day:starttime:endtime]
              This tag limits the time when an active alert is presented on
the NK web page.

              By  default,  tests with a red or yellow status that are
listed in the "NK:testname" tag
              will appear on the NK page. However, you may not want the
test to be  shown  outside  of
              normal working hours - if, for example, the host is not being
serviced during week-ends.

              You  can then use the NKTIME tag to define the time periods
where the alert will show up
              on the NK page.

              The time specification consists of

              day-of-week: W means Mon-Fri ("weekdays"), * means all days,
0 .. 6 = Sunday  ..  Satur‐
              day.   Listing  multiple days is possible, e.g. "60" is valid
meaning "Saturday and Sun‐
              day".

              starttime: Time to start showing errors,  must  be  in
24-hour  clock  format  as  HHMM
              hours/minutes.  E.g. for 8 am enter "0800", for 9.30 pm enter
"2130"

              endtime: Time to stop showing errors.

              If  necessary,  multiple  periods  can be specified. E.g. to
monitor a site 24x7, except
              between noon and 1 pm, use NKTIME=*:0000:1159,*:1300:2359

              The interval between start time and end time may cross
midnight, e.g. *:2330:0200  would
              be valid and have the same effect as *:2330:2400,*:0000:0200.

Jim

On Thu, Jun 7, 2018 at 10:12 AM, Lynn Osburn <user-fd907411ed25@xymon.invalid>
quoted from John Thurston
wrote:
Attempting to prevent “false” cpu alarms during overnight processing, I
have included a line in analysis.cfg thus:

    LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400


However, alarms continue to be generated during the “excluded” hours.


Has anyone else had any difficulty with either TIME or EXTIME entries?


Thanks!

-- 


*----------------------------------------*


*     Jim Louis          \\\\||////          \ ~ ~  /          | @ @ |*


*--oOo---(_)---oOo--*

“It does me no injury for my neighbor to say there are twenty gods, or no
God. It neither picks my pocket nor breaks my leg.”

~ Thomas Jefferson
list Andy Smith · Thu, 7 Jun 2018 19:17:41 +0100 ·
quoted from Lynn Osburn
On 07/06/18 16:12, Lynn Osburn wrote:
Attempting to prevent “false” cpu alarms during overnight processing, I have included a line in analysis.cfg thus:

     LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400

However, alarms continue to be generated during the “excluded” hours.

Has anyone else had any difficulty with either TIME or EXTIME entries?

Thanks!

I always use the DOWNTIME tag in hosts.cfg which not only disables alerts, but ”blues out” the page giving you a nice marker in the event log report.  I have both styles is use eg :-


"DOWNTIME=*:*:2345:0105:Backup Window" \
"DOWNTIME=files,http,msgs:*:0030:0600:Application Optimisation" \

-- 
Andy
list Lynn Osburn · Fri, 8 Jun 2018 20:37:27 +0000 ·
Thought I would mention solution here in case it saves some other folks a lot of head scratching.

It turns out that the analysis.cfg file (and probably the alarm.cfg as well) seem to be whitespace-sensitive.
That is to say, if your "LOAD" command doesn't begin at position 1 on the line, it may be interpreted as a combination condition with the line above.
(of course, one may wish to combine several metrics for a single host, using the indented notation, but that is an intended whitespace)
quoted from Lynn Osburn


From: Xymon <xymon-bounces at xymon.com> On Behalf Of Lynn Osburn
Sent: Thursday, June 07, 2018 9:12 AM
To: xymon at xymon.com
Subject: [Xymon] EXTIME/TIME syntax

Attempting to prevent "false" cpu alarms during overnight processing, I have included a line in analysis.cfg thus:
    LOAD 4.0 6.0 HOST=blueteam EXTIME=W:2200:0400

However, alarms continue to be generated during the "excluded" hours.

Has anyone else had any difficulty with either TIME or EXTIME entries?

Thanks!