Re: AW: [Nagios-devel] MSQL Tables and log files mis-match in data

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: AW: [Nagios-devel] MSQL Tables and log files mis-match in data

Post by Guest »

Cricket "is a good thing" (tm) as Martha Stewart would say in the US.

As you will note cricket uses a dbm... Ethan proposed the same thing - a
dbm sitting between the nagios core and the cgi.

The cgi's would not have to read the config files at all.

Nagios would read the config files on startup and generate the dbm with
appropriate data and update it with status info as well.

Other apps could read the dbm as well and push data into a sql database
for those who need it. This would separate the need to maintain a sql
interface inside the nagios core.

-sg

On Wed, 3 Apr 2002 vol@premiere.de wrote:

> Hi Subhendu,
>
> i think the main reason to convert the config in a DB are the cgi's. The
> cgi's read everytime the config's when a browser is requesting one of the
> webpages. I think the conversion of the config's to a db is a better
> solution than a apache cache modul.
>
> I use one application which "compile's" the configuration into a DB. It is
> 'cricket' (http://cricket.sourceforge.net/), a very fast and easy to
> configure replacement of 'mrtg' (reading values with snmp from
> routers/switches/servers/..., storing them in a rrdtool DB and creating nice
> graph's of the values). I think this can speed up the cgi's a lot.
>
> regards vol
>
> -----Ursprungliche Nachricht-----
> Von: Subhendu Ghosh [mailto:sghosh@sghosh.org]
> Gesendet: Mittwoch, 3. April 2002 08:16
> An: nagios-devel@lists.sourceforge.net
> Betreff: RE: [Nagios-devel] MSQL Tables and log files mis-match in data
> types, any ideas
>
>
>
> On Wed, 27 Mar 2002, Mark Gillett wrote:
>
> > Thanks for the pointer on the future Ethan, I am not sure how many of the
> > Netsaint/Nagios users out here are using the database support, but it
> seems
> > to be a reasonable number. Would you envisage us adding database support
> as
> > a 'patch' or might you consider providing an API against which we could
> > implement any other 'storage service' that we might want to play with.
> >
> > I guess that the alternative might be for someone ;-) to provide a simple
> > SQL-->Files bridge (mmmm sounds a bit like mSQL v 0.1) for those who still
> > want/need db support.
> >
> > Personally I am playing with the database as the files get a little clunky
> > when writing other analysis code and or interfaces to
> monitoring/management
> > systems other than Nagios :-(. With the db tables some of these
> operations
> > are much faster (to code and to perform), especially when log-file
> rotation
> > (archiving) is enabled.
> >
> > Where can the community add most value here ?
> >
> > Mark
> >
>
> I think the config files are files for what Nagios needs from it - an
> initilization. A DB -to- config generator could be built very easily
> allowing you to maintain you configs in the DB yet use Nagios.
>
> On the log aspects, I tend to favor an option of DB with a single column
> table for each entry in addition to the flat files and archive methods.
>
> DB does provide a certain flexibility in generating and sorting for
> reporting purposes.
>
> -sg
>
>
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/lis ... gios-devel
>






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: sghosh@sghosh.org
Locked