For that size of a deployment you will definitely want to use dedicated hardware.
Also, with 300,000 services the standard nagios web interface could end up being quite slow. Our deployment has just over 21,000 services (multiple remote collectors feeding data back into a primary collector, all dual dual-core or dual quad-core Xeons with 4-8GB RAM). Even though the main server is overpowered and has lots of spare server resources, it takes 6 seconds for *any* page to be rendered (we store the Nagios status file on a ramdisk but it still takes several seconds to parse 35MB of text on every page reload). Due to the number of people we have using it (anywhere from 20-40 users refreshing the page twice a minute), we were forced long ago to build a custom front end that is integrated into an existing equipment database (which is also used to build the Nagios config files) using NDOutils to extract the data from Nagios. (I still need to test and implement a better solution than NDO due to the amount of time it takes to repopulate the database after reloading the Nagios configs.) In order to head off any future scaling issues, I've even began abstracting various functionality out of Nagios into external scripts, e.g., sending notifications (sending a Jabber notification takes almost a second for the script to initialize the connection to our Jabber server, which is way too long and causes latency in Nagios when there are multiple host/service issues), adding/removing comments and acknowledgements, and as scheduling downtime (it's hard to usefully save historical comment, acknowledgement, and downtime data using only Nagios). On 07/08/2010 10:20 AM, Ryan C Ash wrote: > Sorry. It probably would of helped to include some of this information. > It would be a large deployment in terms of what I have seen others > using. There could be ~12 servers each with ~1,500 hosts and 300,000 > service checks (almost all NSCA). We expect a lot of service checks per > host so we want to keep the number of hosts homed to each server below > 2,000. I hope this helps. > > Thanks > > BTW if anyone has scalability documentation it would help us do some > server sizing. > > > > -----Original Message----- > From: Jason Gauthier [mailto:[email protected]] > Sent: Thursday, July 08, 2010 9:11 AM > To: Nagios Users List > Subject: Re: [Nagios-users] Running Nagios on Vmware > > > >> Is anyone aware of documentation or test cases showing whether or not >> > running Nagios on VMware is a good idea? I realize the common opinion > is that it>is a bad idea due to I/O but I am looking for something a > bit more in depth. > > >> Thanks >> > > I think it depends on your environment. I'm running Nagios and Cacti on > Hyper-V with 165 hosts and 487 services. It seems to be fine. > Sometimes apache is slow to respond. > > > > ------------------------------------------------------------------------ > ------ > This SF.net email is sponsored by Sprint What will you do first with > EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Nagios-users mailing list [email protected] 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
