database support nagios 2.0

[Ben]

I'm curious how invasive your code is to nagios' code, because it seems 
like it would have to be very invasive to reach your goals, and that 
quickly becomes a maintenance nightmare, both for you and for the 
people that use your code.

One of the things I really liked about my design of Nagios-DB was that 
it doesn't touch the nagios code at all. Of course, that means you 
won't get any benefit from using it unless you also stop using the CGIs 
that come with Nagios, and, being implemented as a NEB module with 
Nagios' current NEB architecture, it means that configuration 
information can't be stored in the database. But those aren't problems 
for me. YMMV.

What I would suggest doing, if you're hellbent on putting everything 
into the database, is to expand the NEB architecture such that NEB 
modules can replace most, if not all, of the configuration parameters. 
That seems like it would be a better use of time to me.


On Apr 13, 2005, at 8:29 AM, Dietmar Ruzicka wrote:

> Hi,
>
> I am currently writing my diploma thesis at the TU Vienna. A part of 
> my work
> is a mysql database interface for nagios. The plan is to develop a 
> databse
> interface which supports almost everything. This means every 
> information,
> which is currently found in the configuration files, the status files, 
> .. is
> written and read from the database. I do this from the scratch based on
> nagios 2.0b2.
>
> The current status is very pre alpha. The configuration is almost 
> finished,
> excluding the nagios.cfg itself. The configuration tables are based on 
> the
> current text configuration, describe in the documentation, excluding 
> the
> template options. The current state of host and services hold in the 
> memory
> of the nagios-core is written to the database too and almost finished. 
> This
> shall replace the retention, status and objects.cache files and is 
> necessary
> for the webinterface. Comments and downtime information is hold in the
> database too. The changes in the webinterface is just started. An 
> optional
> replacement for the nagios.cmd is also included.
>
> The database support should be option to the usual text-based way, 
> which can
> be activated or deaktivated during the configure step.
>
> I am currently using Nagios in a kind of mixed mode. Almost all parts 
> of
> Nagios-core are using the database, but for the most parts of the
> webinterface the information is read from the text-files, except
> configuration, comments, notifications and scheduling queue. Therefor I
> write the informations to the database and to the text-files.
>
> What Do you think, is this a usable idea?
>
> regards
>
> Dietmar
>
>
>
> -- 
> +++ NEU: GMX DSL_Flatrate! Schon ab 14,99 EUR/Monat! +++
>
> GMX Garantie: Surfen ohne Tempo-Limit! http://www.gmx.net/de/go/dsl
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click