On 10 February 2011 17:24 I wrote:
Hi,
I'm having a problem with using first_notification_delay. I'm not
sure if it's a bug or just that I don't understand how it's supposed
to work. ...
I believe I found the answer here:
Hi,
I'm having a problem with using first_notification_delay. I'm not
sure if it's a bug or just that I don't understand how it's supposed
to work.
I have this passive service check to receive traps from a UPS:
define service {
host_name ups-a
service_description
no bug in your case.
first_notification_delay is just to postpone the notification for a
(hard)status change, Nagios won't check the status during the delay
period.
in your example, a notification will be sent at 09-02-2011 07:17:41 to
reflect the critical event at 09-02-2011 07:07:41, no matter
Hi all
Can someone pls explane to me how first_notification_delay works ?
I setup one host with one service for testing. I setup first_notification_delay
for host to 5 and for
service (http) to 10 so i expected that i get nitification after 10 minutes
when i stop http service.
But i always
Hi
As addition to my first post about notification delay.
I made some further investigation and found out some another strange behaviour
(for me) and couldn't find any info in docs.
I have first_nitification_delay for host se to 0 and i have tried change this
setting for service and here are
On Jan 19, 2010, at 11:57 AM, komodo wrote:
Hi
As addition to my first post about notification delay.
I made some further investigation and found out some another strange
behaviour
(for me) and couldn't find any info in docs.
I have first_nitification_delay for host se to 0 and i
I have no experience with this feature and don't have time to dig into it
right now but based on your unreliable behavior I'd suggest you make sure
you don't have multiple copies of nagios running at the same time. If
you've been stopping and starting a lot that may be the case.
--
Marc
