Re^3: Central logging methods and thoughts

Agreed that a simple protocol like IRC has issues with security & integrity. You would have to trust yourself and your colleagues notto be stupid or evil.

With the system you use, do you find that you have scaling problems with the db inserts? I assume that the local daemon will retry if the db becomes unavailable, but what does your app do if the local daemon becomes unavailable?

Comment on Re^3: Central logging methods and thoughts

Replies are listed 'Best First'.
Re^4: Central logging methods and thoughts by radiantmatrix (Parson) on Oct 12, 2005 at 20:40 UTC
We don't tend to have scaling issues with the DB because we have an HA database system. I don't know the details, but there are several "satellite" servers that accept queriers, and together they form a sort of "logical database" that is relplicated, in turn, to a more solid archive. I could be explaining it wrong, as I didn't set it up. The local daemon dying is one of the issues. Until recently, apps dealt with this in undefined ways (by which I mean the authors chose, there was no standard). Just recently, we decided that we'd write app-named files to a specific directory, which the daemon scans and uploads (and cleans) at startup. I have reservations about this, though -- it seems like asking for trouble. Powers that be know there are issues with this too, but no one (including me) has come up with a better idea yet... <-radiant.matrix-> A collection of thoughts and links from the minds of geeks The Code that can be seen is not the true Code "In any sufficiently large group of people, most are idiots" - Kaa's Law	[reply]
Re^5: Central logging methods and thoughts by aufflick (Deacon) on Oct 12, 2005 at 23:05 UTC
great - thanks for the info!	[reply]