[Xymon] Alert testing failing on time criteria
John Thurston
john.thurston at alaska.gov
Thu Mar 6 00:42:22 CET 2014
On 3/5/2014 1:06 PM, Scot Kreienkamp wrote:
> Hey everyone,
>
> Running into something I don't understand trying to test my alerts.cfg.
>
> I have a line in alerts.cfg like so:
> HOST=lzbs1101.na.lzb.hq SERVICE=ADUsers TIME=*:0000:0800
>
> And I'm trying to test it out using this command line:
> xymond_alert --test lzbs1101.na.lzb.hq ADUsers --duration=6 --color-red --time=3:0523:0611
>
> And the result I'm getting back is:
> Failed 'HOST=lzbs1101.na.lzb.hq SERVICE=ADUsers TIME=*:0000:0800' (time criteria)
>
> Can someone help me understand why it's not matching on time? I have it set to every day between midnight and 8am in alerts.cfg, and the timeframe I'm trying to test is within that window. So why isn't it matching?
--time=TIMESTRING The TIMESTRING parameter is the time-of-day for the
alert, expressed as an absolute time in the epoch format (seconds since
Jan 1 1970). This is easily obtained with the GNU date utility using the
"+%s" output format.
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
John.Thurston at alaska.gov
Enterprise Technology Services
Department of Administration
State of Alaska
More information about the Xymon
mailing list