NagiosPluginsNT scaling to 400 sites?

[Justin Hitt]

Roger,

On Feb 19, 2008 8:58 AM, Roger <Roger at nagioswiki.com> 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/vse0120000070mrt/direct/01/
_______________________________________________
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