On Dec 23, 2009, at 6:30 PM, Nicholas Tang wrote: > You could probably also log to Syslog and have it write those logs to a > remote Syslog server rather than writing them locally. That won't require a > network-aware logging module.
THe disadvantage to remote syslog is that the default protocol is UDP, and in my experience is very sensitive to latency. On networks that were less than 1% utilized, I've seen UDP syslog drop over 75% of all the log data. Packages like syslog-ng allow you the option of doing syslog over a TCP connection, but that also has some issues. > Both of those solutions have the added advantage of allowing you to log > multiple webservers' logs to a single physical machine and log, making it > easier to analyze them later. It's actually easier to combine things later and keep them separate earlier in the process. Once they streams are merged, it can be difficult or impossible to separate them out again. -- Brad Knowles <[email protected]> LinkedIn Profile: <http://tinyurl.com/y8kpxu> _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
