Fwd: nagios-service-refresh-rate
Arno Lehmann
al at its-lehmann.de
Sun Apr 3 19:20:02 CEST 2005
Well then,
vivek sharma sharma wrote:
> Well you are right Arno believe me i have read as much time as I got and
> i have not found any reference for the thread behaviour of Nagios.Anyway
> my understanding says that Nagios would open multiple threads for the
> given hosts/services at a time and give the warning/critical messages
> accordingly.
> Again the request is ::plz correct me if i am wrong::
Basically, checks are done serially - you can see this in the scheduling
info. Then, you've got a setting which determines how many checks are
done in parallel. In the example in the manual, it is even explained how
nagios determines which checks to execute in parallel.
As a result of how a unixlike system works, nagios forks the actual
check processes. The results are collected in a sort of result buffer
and "taken" from there with the service-reaper frequency.
How this all works together is explained in some detail in the manual.
You might notice that only one process des the actual messages. Why this
is the case? I can guess it by reading the manual, especially the
sections about why host checks are always serialized and nothing runs in
parallel while nagios determines the host states.
> Also i wanted to know whether this behaviour of Nagios shall not add to
> too much of network traffic if i am going to increase the no. of
> hosts/services and also keeping the time interval to one minute.
The amount of network traffic is a direct result of the kind and number
of checks you do. Over time, it doesn't matter how many checks are run
in parallel - the sum of the checks remains the same over time.
It does not if you "overload" the nagios-server or the network links,
so, when you approach that limit, you will want to fine-tune the check
intervals, number of parallel checks, and service-reaper frequency.
> Plz suggest.
What sort of suggestions do you want? How to setup your monitoring? We
would need more information about the number of hosts, services, the
network saturation resulting from your existing setup, etc. pp.
Arno
> Thanks.
> Vivek.
>
>
> On Sun, 03 Apr 2005 Arno Lehmann wrote :
> >vivek sharma sharma wrote:
> >
> >>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.
> >
> >Vivek, you really should take the time to read the manual. Really.
> >
> >Arno
> >
> >
> >>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
> >>
> >>
> >>
> >><http://clients.rediff.com/signature/track_sig.asp>
> >
> >-- IT-Service Lehmann al at its-lehmann.de
> >Arno Lehmann http://www.its-lehmann.de
>
>
>
> <http://clients.rediff.com/signature/track_sig.asp>
--
IT-Service Lehmann al at its-lehmann.de
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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
More information about the Users
mailing list