Nagios and DB support.
Andreas Ericsson
ae at op5.se
Fri Nov 19 09:25:52 CET 2004
Ben wrote:
> On Thu, 18 Nov 2004, Andreas Ericsson wrote:
>
>
>>>I believe the best reasoning I heard was so that people could easily
>>>modify that configuration via a website. Obviously flatfiles can also be
>>>modified from the web, but it tends to be easier when it's in a database.
>>>
>>
>>If the person writing that webinterface is too stupid to export
>>everything in a nagios compatible way, I don't give much for his/her
>>talent as a coder. More often than not it is also desireable to do
>>several changes, some of which might actually break the configuration
>>(until all changes are done, anyway), before saving it and thus have
>>Nagios reload it.
>
>
> Writing a file in a certain format may not be hard, but transactions and
> concurrency issues are difficult to get right. Why try and likely fail
> when databases have it correct already?
>
Transactions are pointless to use unless several tables needs to be
updated at the exact same time, and the changes needs to be rolled back
if they're not.
> Assuming you want to have multiple people modifying your config files at
> the same time, of course. :)
>
There's still a problem with that when using intermediate database
format, in case several users use the GUI at one time. It's nothing too
hard to solve, but still. I've written a complete one myself and
promptly ran into (and solved) that particular issue.
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Lead Developer
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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
More information about the Users
mailing list