Fwd: nagios-service-refresh-rate
vivek sharma sharma
vivek_222 at rediffmail.com
Fri Apr 1 15:10:57 CEST 2005
Hi Rajeeve,
Yeh i did the same keeping the interval_length is 60 sec. and the normal_check_interval as 1 so it makes the check possible in one minutes.So the refresh rate is now about one minutes.
But in this case now i have 84 services on as many clients so what is the max. time i can expect for a client to be checked is it one minute or Nagios finishes with one and then proceeds with the next one.
I think it must be opening multiple threads say in one minute(in my case now)for multiple hosts and hence every host can get checked in one minute...
Correct me if i am wrong.
Thanks.
Vivek
On Thu, 31 Mar 2005 Rajeeve K Krishnan wrote :
>HI Vivek,
>
>check the value of 'interval_length' in the nagios.cfg file. normally
>it will be 60 which means one interval unit is 1 minute -thus making
>the normal_check_interval into 5 *60 seconds ie 5 minutes
>
>If the 'interval_length' is more than 60 , you will have to either
>decrease the 'interval_length' or normal_check_interval to set
>nagios for executing service checks more frequently
>
>thanks
>Rajeeve
>
>
>
>On 31 Mar 2005 08:27:45 -0000, vivek sharma sharma
><vivek_222 at rediffmail.com> wrote:
> >
> >
> > Dear all,
> > Any suggestions on this.
> > I have to solve this urgently.
> >
> > Thanks.
> > Vivek
> >
> >
> > Note: Forwarded message attached
> >
> > -- Orignal Message --
> >
> > From: "vivek sharma sharma" <vivek_222 at rediffmail.com>
> > To: nagios-users at lists.sourceforge.net
> > Subject: nagios-service-refresh-rate
> >
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: "vivek sharma sharma" <vivek_222 at rediffmail.com>
> > To: nagios-users at lists.sourceforge.net
> > Date:
> > Subject: nagios-service-refresh-rate
> >
> >
> > Dear all,
> > I am using Nagios(r) Version 2.0b version.on redhat linux-9.0
> > My service configuration is:
> > define service{
> > use generic-service
> > host_name flowc.XXX.net
> > service_description check_ping
> > is_volatile 0
> > check_period 24x7
> > check_freshness 1
> > freshness_threshold 60
> > max_check_attempts 3
> > normal_check_interval 5
> > retry_check_interval 1
> > contact_groups noc-support
> > notification_interval 120
> > notification_period 24x7
> > notification_options c,r
> > check_command check_ping
> > }
> > define service{
> > name generic-service
> > active_checks_enabled 1
> > passive_checks_enabled 1
> > parallelize_check 1
> > obsess_over_service 1
> > check_freshness 0
> > notifications_enabled 1
> > event_handler_enabled 1
> > process_perf_data 1
> > retain_status_information 1
> > retain_nonstatus_information 1
> > register 0
> > }
> > define command{
> > command_name check_ping
> > command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 450.0,40% -c
> > 1750.0,98%
> > }
> >
> > But the problem that it shows the service as down only after about ten
> > minutes and also to show the service as up also it shows it after sya ten
> > minutes again.
> >
> > Is it anything related to the above command::basically i wuld like to know
> > that when we say xx% loss or xxms latency then after how many tries this
> > %age is calculated how the command is actually working.
> >
> > Can anybody suggest on what may be the issue here...
> >
> > Thanks.
> > Vivek.
> >
> >
> >
> >
> >
> >
> >
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by Demarc:
>A global provider of Threat Management Solutions.
>Download our HomeAdmin security software for free today!
>http://www.demarc.com/Info/Sentarus/hamr30
>_______________________________________________
>Nagios-users mailing list
>Nagios-users at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20050401/265a0a12/attachment.html>
More information about the Users
mailing list