nagios scaling and server spec

[kyle.odonnell at gmail.com]

Hi Patrick,

Ive currently got one server doing everything (and more) hosting 600
hosts and ~6000 services.  The main server itself won't be doing any
actual execution, it will just be receiving passive alerts.  I would
still like to keep one master, but just use multiple slaves that feed
into it.

Out of curiosity, are you using a correlation system at the top of
your multi-master setup?

--kyleo

On 6/29/07, Morris, Patrick <patrick.morris at hp.com> wrote:
> > I am trying to spec some hardware for a nagios environment capable of
> > ~5000 hosts, and ~50,000 services.
> >
> > I am wondering if anyone has any hardware recommendations for the
> > active-service-check machines (or polling), and the (hopefully) 1
> > centralized passive-service-check recipient.  And, if anyone believes
> > the central server can handle that many events.
> >
> > I currently have an all in one machine monitoring ~600 hosts and ~5000
> > services.
>
> There are a lot of variables there I don't know, but it may be difficult
> having one box keep up with that many check submissions, depending on
> how much overhead you've worked into the system.
>
> It's probably doable, but I've had to hack a lot of checks and restart
> scripts onto an installation I've got here with about 1,500 hosts and
> 10,000 services, and it still can get hairy if a lot goes wrong at once.
> We're replacing it with a setup with multiple masters, and that's
> working a lot better.
>

-------------------------------------------------------------------------
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
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