Has anyone found a way to get around this? Or a better technique to conglomerate logging from multiple web servers reliably?
Any ideas on good log4net log file analysis tools too (plain text not XML) – apart from good ‘ol grep of course 🙂
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Has anyone found a way to get around this? Or a better technique to conglomerate logging from multiple web servers reliably?
Any ideas on good log4net log file analysis tools too (plain text not XML) – apart from good ‘ol grep of course 🙂
The 1024 byte limit is part of the syslog RFC (section 4.1), as is UDP transport which doesn’t have guaranteed delivery (in case you worry about log lines lost in the ether). I think syslog-ng can solve both these issues, but I’m not a syslog expert.