The NC_Net EventLogCheck Time field at a minimum should be set to a value greater than :
THe Check interval + the average Latency
This way it will catch events that happen right after the check happens.
Please note depending on your monitoring preferences (For example retry interval) and procedures you may want to adjuct the Time to be even larger.
Note: It is recomended to always use the latest version of NC_Net. Each version of NC_Net typically includes bug fixes and enhancements.
Good luck
Tony
On 11/10/05, Horvath Tamas <[EMAIL PROTECTED]> wrote:
Hi!
I'm going to install NC_Net V1_x on several Windows boxes and use it with
Nagios. I used in other sites an other plugin, but I would like to try
Nc_Net because it can be used instead of two or more separate plugin. But
I'm a bit confusing about Event Log Check behavior of Nc_Net.
According to the documentation of the latest (2.28) version: "the third
parameter is for time interval in minutes (how old do you want the events
entry to check)".
If I query event log via Nagios in every 10 minutes how does Nc_Net handle
service check latency?
I mean the following: query event log at time 't0' and give time
interval=normal_check_interval, for example 10 minutes. After 10 minutes
Nagios try to query the event log again, but due to latency the query is
sent at time 't0+610 second'. What happens if a log entry is written to the
event log at 't0+602 second'?
Thanks in advance, Tamas!
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nagiosplug-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null