Problem Updating through MySQL

[Marc Powell]

> -----Original Message-----
> From: Ricardo David Martins [mailto:ricardo.martins at gmail.com]
> Sent: Monday, September 06, 2004 11:34 AM
> To: Marc Powell
> Subject: Re: [Nagios-users] Problem Updating through MySQL
> 
> Hi,
> 
> i have been doing some more tests and i now realize that that the CGIs
> alert history is NOT written in a mysql table. Instead this is done on
> a file (var/nagios.log). I dont understand the reason for this. The
> compilation
> parameter referred mysql data base to all external data, just not
objects.
> 
> How can i have all logged data on a mysql data base. What am i missing
> here?

Nagios does not log historical data to the database, just current
status. It was simply a design decision by Ethan. In fact, all database
support is being removed from the core operation of the program in the
future, depending instead on the development of event handlers to
implement DB support. I don't know if mysql supports it but with pgsql
we use a trigger to copy the data to a retention table on UPDATE. The
CGI's don't reference this, of course, but we use it for our own scripts
(after it's copied to SQLServer.

> I have read about PerfParse... does this do the trick?
 
I don't know. I've never used it.

--
Marc



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id808&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