Nagios with database support

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Daniel Szortyka
> Sent: Thursday, July 07, 2005 11:47 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Nagios with database support
> 
> Hi,
> 
> I always had a question... or a doubt... The nagios database support
> store what exactly?
> 
> Example...
> 
> Can I save my nagios.log and status.log on my mysql..? I say that
> cause in 1.x version, when I go in "Aviability" of hosts or services,
> frequently I had a error result... the hosts always stay with 100% of
> a some result.... With the 2.0b I dont have more this error...

In the 1.x tree, database support consists solely of storing current
host, service and program status data. No historical data is stored in
the database. The CGI's used the database info for current information
and the nagios.log archives for historical data (trends, availability,
etc).

With the 2.0 development version, all database support has been removed
from the core code in favor of the NEB (Nagios Event Broker) which
allows for greater flexibility and a plugin like approach. The
previously mentioned nagios-db project is one such plugin that emulates
the 1.x database support. I believe that it also stores historical data
in the database as well. The _key_ difference is that the core nagios
processes and CGIs will _always_ use flat files for everything. To use
the database stored information you'll either need to use the PHP
scripts included with nagios-db or create your own.

It's impossible to guess what your availability report problem might be
with so little specific information. If you want help with that, post
specific details about the type of report you are running, the time
period, initial state option, etc as well as the log entries for that
host in nagios.log and the archives within that time period as well as
the backtracked archives that you are specifying. Chances are that
Nagios isn't able to find any log entries within your time period for
that host or service or can't determine the initial state within the
time period or backtracked archives.

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
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