Actually, maybe there is a potential issue here. Wouldn't the countdown
timer restart if the service is restarted or configuration reloaded? In a
new and changing environment like mine, this happens all the time. Anyway,
just to throw out this concern as well...
Thanks again,
Mark
On , [email protected] wrote:
Hi Jan, I think what you are saying is definitely true after thinking it
through a bit more. Thank you for replying.
I still would like to know if setting an exact trigger time is possible
within Icinga. Can anyone confirm?
Thanks,
Mark
On , [email protected] wrote:
> Hi, I don't think this will be a problem: If next time the nsca fires
on 09:05 again, the threshold will NOT wait until 11:00 next day, but
will trigger the alert at 10:05 (after 25 hours), as configured. The
gurus might correct me if I'm wrong. RegardsJan Dreyer From: Mark Creamer
[mailto:[email protected]]
> Sent: Tuesday, June 28, 2011 4:33 PM
> To: [email protected]
> Subject: [icinga-users] Setting "Stale Update" passive check I have
some passive checks set up that currently run a "service_is_stale"
command if a freshness_threshold is reached. So basically, a host that is
being monitored runs a job that includes a command to send an update
message to Icinga via send_nsca. That message gets received, and the
freshness_threshold starts counting down. A typical one is supposed to be
received every 24 hours, so the countdown timer is set to (24x60x60)+3600
seconds, basically 1 hour past the 24 hour deadline. If the message has
not been received in that amount of time, the service_is_stale command is
triggered, causing the monitored service to go critical.
> My question is, rather than use a countdown timer, is it possible to
tell Icinga to trigger the alert at an exact time? Example, if a job is
supposed to run every day at 9:00 AM, can I set the service_is_stale
command to run at 10:00 AM every day if the success message has not been
received?
>
> The reason I thought this might be better is, let's say for whatever
reason, the message that should have been received by Icinga was received
at 9:58 AM, rather than around 9:05 as normal. This is still within the
threshold so no alert is triggered, but now the countdown timer is going
to wait for 25 hours from 9:58 AM, not 9:05. If this happens enough
times, pretty soon the freshness interval is way off its intended timing.
>
> I'm fairly new to Icinga/Nagios, so maybe this is an easy thing to do
but I haven't found it yet. Thanks for your assistance.
> --
> Mark
>
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
