Distributed setups

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Tobias Klausmann
> Sent: Monday, July 02, 2007 4:52 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Distributed setups


> Even if the central machien does all the notifications (as we're
> planning), completely dis/enabling service/host checks would have
> to be distributed from the central machine to the checking
> machines.

How often do you really do that? I've found that scheduled downtime fits
99% of situations and those that that it doesn't (long term outages),
editing the config on the master then rsync/scp and reload on the
collector works just fine.


> Or is the usual setup to let the useres access the web interface
> of each "checker machine"? Then how do people know which checks
> are run from which machine?
> 
> If the central machien only does the "webservice job", i.e.
> notifications are handled on the checking machines, how are
> sceduled dowtimes, acknowledgements etc handled?

We do everything on the central machine. Our collectors just collect and
send results inward. Users all use just the central machine. Scheduled
downtimes, acknowledgements, etc don't need to propagate out if you do
all your management and reporting from the central machine.



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