> * Standard log files or couchdb/mongodb are easily manageable > * Relationnal databases are more complex and not best suited for this > purpose imho. Standard logfiles are easily manageable if you copy and move files. Parsing lines in log files is far from easy. Searching logfiles and breaking the lines up in host/servicedescription/command/state etc (like mk-livestatus does) requires writing code. There are no indices etc... Sqlite is a file and a SQL-API, not more, no processes, no startscripts, just a python module available everywhere. Very convenient to select lines from a log and have variables for host- and servicenames etc.. automatically filled. CouchDB/MongoDB are processes which require extra attention. I doubt that the API is more simple that sqlite. And i doubt there is less code necessary. I don't see what item1 (logfiles) and item3 (couch/mongo) have in common. IMHO sqlite is the best compromise between simplicity and performance, that's why i decided to use it in the livestatus module.
Gerhard __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 5765 (20110106) __________ E-Mail wurde gepruft mit ESET NOD32 Antivirus. http://www.eset.com ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
