consider distributed monitoring
On Fri, Feb 11, 2011 at 10:49 AM, Breandan Dezendorf <brean...@dezendorf.com> wrote: > On Thu, Feb 10, 2011 at 9:12 PM, Yueh-Hung Liu <yuehung....@gmail.com> wrote: >> nothing will be known without checking. >> you want more precise data you have to do more checks, that is, >> decrease the "check_interval" value. > > And the lower you set the check_interval, the harder the servers have > to work to keep up with all the checks. While the servers we are > running could very well run all 5000 service checks every 5 minutes > (or even faster), it would chew up a lot of our growth capacity for > the server. > > -- > Breandan Dezendorf > brean...@dezendorf.com > bwdez...@gmail.com > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > 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 > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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
