Depends on the amount of alerts / hardware. I've got about 1000 checks, 120 hosts spread across 4 "slaves", we get few alerts per day (50 or so in 24hrs). I have it running in a VMware server VM using dual (2ghz opteron) processors and 1gb ram it sits between 0.00 an 0.23 so pretty much nothing
It previously ran on one machine with 1 1.7ghz athlon and 1.5gb ram, along with many other custom tools, the average load was about 4.00 or so Hope that helps. chiel wrote: > Hi all, > > I thinking about to do all of my checks trough slave servers using nsca and > to use one master server for notification (e-mail and sms) and the nagios > website. > The load will spread over the slave servers. But I wondering what load I can > expect on the server that only does the notification and website. > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
