Question

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 :)

Was it helpful?

Solution

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.

OTHER TIPS

I read about logFaces on another question, or you could use a socket appender and write your own server. logFaces describes itself as a "Log server, aggregator & viewer" but I'm yet to try it.

The database-based appenders are great for collecting logs from multiple servers.

The limitation is imposed by the syslog itself, not the appender.

I do not know about log4net, but NLog works perfectly ok with "shared" file target - i.e. multiple processes can write in one and the same file.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top