Nagios scalability issues

[Jason Martin]

The distributed monitoring setup in Nagios is designed to handle this problem,
instad of pushing the scheduling to the remote hosts instead create a
second layer of Nagios hosts. You can create one central host to handle
all the notifications and have the distributed Nagios hosts push
their results up to it via the Obsessive Compulsive Service Processor.

-Jason Martin

On Mon, Jul 19, 2004 at 10:30:30PM +0300, Cristian M. Streng wrote:
> monitoring engine - it's a lightweight client-server system that moves the 
> scheduler part from the main server to the individual machines. This way 
> each machine schedules its ~10-20 service checks, and reports back to the 
> server the changes in the service status. And it fixes all of Nagios's 
> problem - at least all that matter to me: the main server becomes less 
> loaded, and the network load is also much reduced. The server part of my 
> application just collects the results from client machines and writes them 
> to a database, so that adds practically no load to the server machine. I'm 
> planning on writing another component that would take these results and 
> send them to nagios - but I have a few questions. What's the best way to 
> send check results to nagios? Will the external command interface work? 
> I'm also interested in the scalability of this feature.
-- 
I'm so broke, I can't even pay attention.
This message is PGP/MIME signed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 211 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040719/b90eaa6d/attachment.sig>