Fellow Hobbitiers...
Some may remember an issue I raised a few weeks back with regard to the TIME option in the hobbit-alerts config in that TIME was not being honoured and so we were getting alerted during blackout time periods that were set. This still looks like it's an issue in the snapshot I downloaded 3days after the beta release.
Has anyone got any other ideas, is TIME only honoured on built in checks or something along those lines as it's the ext scripts that are causing the alerting (they are sending results to hobbit and hobbit does the actual alerting).
Some information...
notifications.log
Sun Jun 18 21:19:37 2006 xxxxx.aq (10.6.2.2) support [139] 1150661977 0
Sun Jun 18 21:24:21 2006 xxxxx.aq (10.7.2.2) sysalert [137] 1150662261 0
Sun Jun 18 21:24:21 2006 xxxxx.aq (10.7.2.2) support [139] 1150662261 0
Sun Jun 18 21:25:21 2006 xxxxx.aq (10.8.2.2) sysalert [137] 1150662321 0
Sun Jun 18 21:25:21 2006 xxxxx.aq (10.8.2.2) support [139] 1150662321 0
Sun Jun 18 22:20:01 2006 xxxxx.aq (10.6.2.2) sysalert [137] 1150665601 0
Sun Jun 18 22:20:01 2006 xxxxx.aq (10.6.2.2) support [139] 1150665601 0
hobbit-alerts.cfg
HOST=*
MAIL=sysalert SERVICE=aq FORMAT=PLAIN REPEAT=1h COLOR=yellow
MAIL=support SERVICE=aq COLOR=RED FORMAT=SMS DURATION>5 REPEAT=1hTIME=W:0900:1700 STOP
(these are lines 135 and 136 so it looks like it's ignoring them totally, although in bb-hostsvc.sh it shows them laid out properly with the correct blackout times listed against the services). As you can see from the information above even though the aq service is set to only alert W(eekdays) between 0900 and 1700 we were still getting alerts over the weekend.
I also have the same problem with another service, this one was just easiest to get the information for.
Regards,
Mike Rowell
This email has been scanned for all viruses by the MessageLabs service.