Right, well, Nagios 1 database support wasn't really anything other than
putting the flatfiles into flat tables. The schema of Nagios-DB is quite
different, but the fundamental issue is still one of namespace. If Nagios
instance A has host foo and Nagios instance B also has host foo, it's not
at all clear (to me) how a unified interface would deal with that.
The interface I wrote also mimics the default UI in that it shows some
nagios config options. But if you have multiple nagios instances, again,
it's not clear how to display conflicting settings without adding another
level of namespace.
Here's one route you might take. Have each Nagios instance write to a
seperate database. Also, have a table someplace that lists the databases
that are being used and some label for each. Then, alter the PHP UI to
read that index table pull reports from each database listed in it, and
generate unified pages accordingly. The PHP is pretty simple (I didn't
even know the language a few weeks ago), so I wouldn't expect this to be
all that hard. Or scrap the PHP and use whatever language you desire.
There's almost zero reporting logic in the actual UI, so it should be
pretty easy to remake them again.
On Thu, 23 Dec 2004, Jason Martin wrote:
> On Thu, Dec 23, 2004 at 10:27:24AM -0800, Ben wrote:
> > What are you trying to accomplish by running multiple Nagios instances?
> I'm looking to allow several different administrative groups to
> run their own Nagios instances while still having a central
> console for the overall status.
>
> > Anyway, there aren't any concurrency issues, if that's what you're asking.
> In Nagios 1.x two instances in the same DB would continually
> overwrite each other's data.
>
> -Jason Martin
> --
> "No good deed goes unpunished" - Clare Booth Luce
> This message is PGP/MIME signed.
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]