I had similar issue of not knowing the alerting triggering process,

Please look though following FAQ and look for example of alerting debuging example.

"bin/hobbitd_alert --debug --test t-rh9.mywork.com PROC "

http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#Q._...

T.J. Yang

To: hobbit at hswn.dk From: DKDeckert at Hormel.com Date: Fri, 3 Jul 2009 13:52:33 -0500 Subject: [hobbit] DOWNTIME not working

Hellow fellow xymon users,

I am stuck. I have a custom test on a host that only runs from 7am to 11am. The rest of the time it does not run. I dont want it to show up purple just blue.

I will put exactly what my bb-hosts file shows

0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh DOWNTIME=rouge_detector:*:1100:0700

i tried this and it should work

I've also tried

0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh "DOWNTIME=rouge_detector:*:1100:0700" 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh "DOWNTIME= [rouge_detector:]*:1100:0700" 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh DOWNTIME= [rouge_detector:]*:1100:0700 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh SLA=*:1100:0700

I dont know why the "rouge_detector" test will not go blue. I just dont want it to show up purple from 11am till 7am the next day...

any ideas...Is this even the correct format ...

In bb-hosts man pages it says

DOWNTIME=[columns:]day:starttime:endtime:cause [,day:starttime:endtime:cause]

thanks guys....you guys save my job :D

Notice: This communication is an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. § 2510. Its disclosure is strictly limited to the recipient(s) intended by the sender of this message. This transmission and any attachments may contain proprietary, confidential, attorney-client privileged information and/or attorney work product. If you are not the intended recipient, any disclosure, copying, distribution, reliance on, or use of any of the information contained herein is STRICTLY PROHIBITED. Please destroy the original transmission and its attachments without reading or saving in any matter and confirm by return email.

Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutori...

The syntax of your first rule is correct but I think only yellow or red status can be reset with DOWNTIME (not purple).

From bb-hosts(5):

... DOWNTIME=[columns:]day:starttime:endtime:cause[,day:starttime:endtime:cause] This tag can be used to ignore failed checks during specific times of the day - e.g. if you run services that are only monitored e.g. Mon-Fri 8am-5pm, or you always reboot a server every Monday between 5 and 6 pm.

       What happens is that if a test fails during the  speci-
       fied  time,  it is reported with status BLUE instead of
       yellow or red.

...

You can ignore purple alerts from the "rouge_detector" with an IGNORE directive in hobbit-alerts.cfg. For example:

HOST= Pro015 SERVICE=rouge_detector COLOR=purple TIME=*:1100:0700 IGNORE

The purple status will show up in the event log though.

Dominique

DKDeckert at Hormel.com wrote:

Hellow fellow xymon users,

I am stuck. I have a custom test on a host that only runs from 7am to 11am. The rest of the time it does not run. I dont want it to show up purple just blue.

I will put exactly what my bb-hosts file shows

0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh DOWNTIME=rouge_detector:*:1100:0700

i tried this and it should work

I've also tried

0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh "DOWNTIME=rouge_detector:*:1100:0700" 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh "DOWNTIME= [rouge_detector:]*:1100:0700" 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh DOWNTIME= [rouge_detector:]*:1100:0700 0.0.0.0. Pro015 #NOCOLUMNS:cpu ftp ssh SLA=*:1100:0700

I dont know why the "rouge_detector" test will not go blue. I just dont want it to show up purple from 11am till 7am the next day...

any ideas...Is this even the correct format ...

In bb-hosts man pages it says

DOWNTIME=[columns:]day:starttime:endtime:cause [,day:starttime:endtime:cause]

thanks guys....you guys save my job :D

Notice: This communication is an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. § 2510. Its disclosure is strictly limited to the recipient(s) intended by the sender of this message. This transmission and any attachments may contain proprietary, confidential, attorney-client privileged information and/or attorney work product. If you are not the intended recipient, any disclosure, copying, distribution, reliance on, or use of any of the information contained herein is STRICTLY PROHIBITED. Please destroy the original transmission and its attachments without reading or saving in any matter and confirm by return email.