> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Stephen Joy
> Sent: Monday, February 20, 2006 4:46 PM
> To: [email protected]
> Subject: [Nagios-users] MySql Status Data
> 
> Hello All,
> 
> I am trying to get Nagios V1.3 to write its status data to a MySql
> database but am not yet quite there.
> 
> So far i have created the database 'nagios' and understand from the
manual
> that you must create the three tables (named programstatus,
hoststatus,
> and servicestatus) but what are the fields?? This does not seem to be
> covered in the manual.

http://nagios.sourceforge.net/docs/1_0/xdata-db.html

"Table Definitions

In order to read from or write to a database, you first have to create
it and setup some tables to hold your data. Note: If you are storing
more than one type of external data in databases, you could create
separate databases for each type of data (comments, status info, etc.)
You could also keep everything in a single database (different data is
kept in different tables). In your database(s) you're going to have to
setup the appropriate table(s) so Nagios can actually read/write data.

****** Important: Scripts for creating tables for all types of external
data for both MySQL and PostgreSQL databases can be found in the
contrib/database/ directory of the distribution."  ******

$ pwd; ls 
/usr/local/src/nagios-1.3/contrib/database
create_mysql  create_pgsql  README

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to