On Tue, 2010-05-18 at 15:31 -0300, Marcel wrote: ... > It seems that nagios don't do the best job at taking the hardware to > its real limits. > > When I have more than, say, 10k checks, I start seen check latency > rises and there just isn't anything that could be done, even > distributed monitoring have the nagios.cmd write-lock bottleneck.
How busy was the CPU and disk? > I'm asking if there is by design that nagios don't thrases the server > when the number of checks reaches certain limits. I don't know enough about the design yet to know about throttling, but the Nagios FAQ says that multiple copies of Nagios can run in one machine if certain files are separate. So if one copy isn't saturating the machine, you might be able to run multiple "distributed" copies in one machine. Next we'll hear from someone who knows better why that is not a good idea. ------------------------------------------------------------------------------ _______________________________________________ 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
