If you aren't actually using the data from NDO, there is little point in
creating the DB.
I would probably not use NDO to write directly from the satellites. Here is why:
- Double the network traffic. The satellites have to send check
results AND database writes.
- Less reliable. How would you keep the master server from writing the
same information to the DB that a satellite has just written, and messing up
the data?
- NDO can be a serious performance bottleneck; you wouldn't want your
satellites to be a potential point of failure in terms of performance.
- If the satellites are behind a firewall, it may not even be possible
to write directly to the DB.
From: Scott Ward [mailto:[email protected]]
Sent: Friday, June 11, 2010 6:05 AM
To: Nagios Users List
Subject: Re: [Nagios-users] Large Installation
We are going to be using distributed monitoring for sure. We just cannot
decide whether we should use NDO to write directly to the database or us NSCA
to send back to the master server. Any suggestions?
Is there a frontend that actually uses the information in an NDO db? From what
I've read it looks like the default Nagios front end uses text files.
~Scott Ward
On Fri, Jun 11, 2010 at 4:48 AM, Martin Melin
<[email protected]<mailto:[email protected]>> wrote:
On Thu, Jun 10, 2010 at 21:55, Kevin Keane
<[email protected]<mailto:[email protected]>> wrote:
Config file maintenance can be improved to some extent with careful design of
the config files, as well as tools. It is an issue that I am running into with
a relatively small installation with 80+ hosts and 400+ services. My
installation is highly heterogeneous and very dynamic, which makes config file
maintenance a nightmare. Having to restart Nagios after a configuration change
doesn't help either. On the other hand, a network with 2000 identical machines
is probably going to be much easier to manage than my type of network.
Nitpicking or helpful tip, you decide: Nagios reloads config changes on SIGHUP,
you don't have to do a restart. A full restart can take a while on a
sufficiently sized installation so having to do one for every change would
indeed be a PITA, but I've never seen a reload take more than a few seconds.
Cheers
Martin
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Nagios-users mailing list
[email protected]<mailto:[email protected]>
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
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Nagios-users mailing list
[email protected]
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
