Large Installation

[Matt Simmons]

Make sure to read these pages:

http://nagios.sourceforge.net/docs/3_0/tuning.html
http://nagios.sourceforge.net/docs/3_0/largeinstalltweaks.html

Also, if you're monitoring 800 machines across WANs, you might look
into distributed monitoring:
http://nagios.sourceforge.net/docs/3_0/distributed.html

Let us know how it goes!

--Matt

BTW, what are you using for your config maintenance?


On Thu, Jun 10, 2010 at 1:51 PM, Scott Ward <13.sward.13 at gmail.com> wrote:
> We are looking to do an large installation of Nagios. Is it possible to
> monitor over 800 machines and over 14000 services?
>
> Has anyone tried doing anything like this? If you have how successful was it
> and how did you configure it?
>
> ~Rultax
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> 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
>



-- 
LITTLE GIRL: But which cookie will you eat FIRST?
COOKIE MONSTER: Me think you have misconception of cookie-eating process.

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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