As I've mentioned before, I would like to kill off the DB support (as
it current stands) in Nagios 2.0. This includes MySQL/PostgresQL
support for the following data types:
- status data
- retention data
- comments
- downtime
- extended info
Is there any really good reason why people want/need this data to be
stored in a database?
Extended info is not dynamic like the other items on the list - its
more static like object definitions. If people want to store this
info in a db, it would be fairly simple to just generate a template-
based config file from the db rather than having the CGIs read
directly from the database.
I don't see any really good reasons for keeping DB support around for
the rest of the data, but I'd like to hear some comments before I
start nuking code.
Ethan Galstad,
Nagios Developer
---
Email: nagios@nagios.org
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: nagios@nagios.org