Hello! Noone has noticed this behaviour?
Thank's Simon Il 13/08/2012 10:19, Simone Felici ha scritto: > > Hello to all! > > I'm using the macros "HOSTDURATION" and "SERVICEDURATION" to notify how many > time the host or > service is in the current state. Looking on the definition: > > host: > A string indicating the amount of time that the host has spent in its current > state. Format is "XXh > YYm ZZs", indicating hours, minutes and seconds. > > service: > A string indicating the amount of time that the service has spent in its > current state. Format is > "XXh YYm ZZs", indicating hours, minutes and seconds. > > Assuming I've a host as follow: > ping hostckeck with 2 retries (60secs) > service with 3 retries (60secs) > host checks made only on demand, when required > > When the host goes in DOWN HARD STATE (2 checks made, more than 60secs > passed) the notification is > sent with HOSTDURATION = "0d 0h 0m 0s" (or some secs more). > When the service enters in CRITICAL HARD STATE (3 checks made, more than > 120secs passed) the > notification is sent with SERVICEDURATION = "0d 0h 2m 0s" (or some secs more, > depends on latency I > think). > > So, it seems the HOSTDURATION timer starts when the host is in HARD STATE > down, but the > SERVICEDURATION timer starts when the service is in his first SOFT STATE > CRITICAL. > > Is this correct? A bug? I think the service is in the correct situation. > > Thank's a lot > > Simon > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
