On Mittwoch, 12. September 2007 15:24 Anne wrote: > I get your point but it is against good design principles. > Optimization of logfiles and usage of external tools is the way to > go, which has already been said by Paul.
I've already given one example where it has advantages: 1) Our customers should be able to check logs themselves. Via DB, it's easy to SELECT .. where customer='xxx' and date=yesterday; that would be horribly slow when parsing the normal text syslog. 2) Another thing is you can save a lot of entries. On a busy server, you get something like - login cust 1 - login cust 2 - logout cust 1 - login cust 3 - logout cust 4 - logout cust 3 blabla. When using the DB, you can compress that to just one row per customer login, by using fields login_time, logout_time (and others), which is normally what admins want to see when a customer calls with a problem. At least, I usually do "grep customer <log|less" and search the bits together. Or just "less log" and then search within, but that's not the best also. But I don't want this to become a flame war over "what's better"?, and the dev said he doesn't like it so it should end now ;-) mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
pgpl3okgpMSyC.pgp
Description: PGP signature
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
