opdb

• It writes all the nagios statistics like host state changes, service state changes, schedule downtimes, comments and so on in the database opmon.
• All performance data is written to the datadase opperf and each host has a dynamic created table in the format: perf_ where host_id comes from the opcfg database. This strategy was tought to easy administration, increase query speed and update, instead of having a huge table, we split them in hosts.
• In the opperf database there is a table service_metric that contains all the metrics a host and service have.

• Open the pkg inside the modules directory of a nagios 3.x
• Edit opdb.c and set up these 3 lines

 /* This file has the mysql database host, user and password, a example file is supplied */
 #define DBCONF "/usr/local/nagios/etc/db.php"
 /* In case the broker can't write to the database, it writes the queries to a file, so 
 they can be importer later on, both for opmon statiscts and performance database 
 */
 #define FAILED_QUERIES_FILE "/usr/local/nagios/var/opmon.sql"
 #define PERF_FAILED_QUERIES_FILE "/usr/local/nagios/var/opperf.sql"

• In the directory modules run to compile it

• nagios 3.x
• Mysql database
• opmon-opcfg - the broker reads the host_ids and service_ids out of the opcfg database

The opdb project is a nagios broker that writes statistics and performance data to a mysql database.