|
|||||||||||
|
central logging to a database
From: Martin Marcher <martin.marcher(at)gmail.com>
Date: Wed Jun 27 2007 - 17:02:31 EDT
we're not exactly an ISP but I guess people subscribed to this list are the ones with the best knowledge, feel free to point to the appropriate place if i'm absolutely OT I'm planning on setting up a central log server. I'd like to log everything from the last 2 rotations (guess in my case 2 days should be enough) locally for a fallback and also log everything to the sql database - is that even a smart approach (logging to 2 places, i know that i need to know myself how much fallback i need in case the central log server goes down) Now initial googling pointed me to 2 solutions and an interesting info
The info i found while googling (which of course i was too dumb to bookmark) was about some kind of standard schema used for database logging so that one, at least in theory, could switch backends with less efforts since a bunch of tools (i think it was monitorware but that led me to some commercial site besides phplogcon for which i read a lot of bad reviews.) rely on that schema. Is there something like that (at least some commonly used schema) or am i on my own?
thanks
-- To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Wed Jun 27 17:15:44 2007 This archive was generated by hypermail 2.1.8 : Wed Jun 27 2007 - 17:20:02 EDT |
||||||||||
|
|||||||||||