[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Unwanted delay in hobbit alerts
- To: hobbit (at) hswn.dk
- Subject: Unwanted delay in hobbit alerts
- From: "Brian Bernstein" <bernie9998 (at) gmail.com>
- Date: Wed, 12 Jul 2006 16:26:50 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=HlzuqBlT0+OQnfVo0WqGrkh6eUQ+BeKPYjB2pWZZlcxSCyfXSoK0tmpSSoif+HaaKt6Ctsf+Mb/qYgWvMm4Z0c/Jk5XmYBgGJj5dr62hGemhinzrPxBkkHEaEH24NeVYlVRpA2Wg/2XTjCSctfH4HWOa5t41rH5Xe23a8bUAemw=
It seems that hobbitd_alert for whatever reason, is sending alerts
only once every half hour.
In other words, if I was to test an alert as such:
bbcmd hobbitd_alert --test [hostname] [test]
It will immediately output that it found a matching rule, and states
the action being taken
(mail -s etc. . .), however, the notification will not come up in the
notifications.log or in the mail server logs until either :06 or :36
past the hour.
Also, the output of the resulting messages in the alerts are time
stamped just before the message is sent/received as opposed to when
the command was first called to run the test.
I have not tested to see if this happens when a machine actually goes
down (the test in question for this particular alert), just with the
test option in hobbitd_alert (actually, the host I've chosen for the
test was already down).
The alert rule in question is rather simple:
HOST=* SERVICE=conn
MAIL [user] (at) [server].[tld] RECOVERED
Any help in this would be greatly appreciated.
-Brian