Re: [Nagios-users] NagiosPluginsNT scaling to 400 sites?
Hari, On Feb 19, 2008 10:12 AM, Hari Sekhon <[EMAIL PROTECTED]> wrote: > If they don't appear in the sidebar, then you're unlikely to type in the > url to hang the browser even if you knew what it was. Excellent, commented out "Detail" and "Grid" options from 'side.html' ... definitely keeps people from bogging down the server with 'status.cgi' and still let's people drill down specific selects. Thank you. Best, Justin -- Attention Sales And Marketing Professionals Who Serve B2B Executives http://hittpublishingdirect.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
Re: [Nagios-users] NagiosPluginsNT scaling to 400 sites?
Justin Hitt wrote: > -- Some of the "Monitoring" menus become useless. For example, "Host > Detail" will take forever to load and "Hostgroup Grid" will kill > Internet Explorer. It would be nice to disable these menu items. > Just go to side.html on the nagios server and edit the html to remove the lines referencing those pages then, it's easy to do and that way they won't appear in your interface for you to accidentally click on them and make your system hang. If they don't appear in the sidebar, then you're unlikely to type in the url to hang the browser even if you knew what it was. -h -- Hari Sekhon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
Re: [Nagios-users] NagiosPluginsNT scaling to 400 sites?
Roger, On Feb 19, 2008 8:58 AM, Roger <[EMAIL PROTECTED]> wrote: > I'm wondering if one centralized Nagios server can use the NagiosPluginsNT > project (http://tinyurl.com/2y8ykr) to effectively monitor certain critical > internal services from that location. I'm monitoring 3,100 hosts at one location and 215 at another with very few issues. As long as you get as much work off the server, distributed to hosts (i.e. use NSCA or some kind of passive push) you'll be fine as your volume grows. If you are using virtualization, then you need a balanced model where you are using passive only on the global zone or host operating system, then light polling on individual zones. The model you describe sounds like it will work. There is a point where you'll need to optimize your top end hardware. My 215 sites is a test bed in a Solaris zone on a P4 2.8Ghz single processor ... needless to say, it doesn't run as clean as the larger installation. Some common problems you'll face: -- Your 'checkresults' queue may grow in size with stale checks because of the time it takes to cycle through all the hosts. Passive checks reporting to a main console will improve this and so will a more meaty head server. -- Some of the "Monitoring" menus become useless. For example, "Host Detail" will take forever to load and "Hostgroup Grid" will kill Internet Explorer. It would be nice to disable these menu items. Best, Justin -- Attention Sales And Marketing Professionals Who Serve B2B Executives http://hittpublishingdirect.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
