tag:blogger.com,1999:blog-8942599.post7319811166708813768..comments2010-02-14T04:18:49.362-05:00bryanhttp://www.blogger.com/profile/01332614158223702009noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8942599.post-10314932125164905622010-02-14T04:18:49.362-05:002010-02-14T04:18:49.362-05:00@shlomik<br />you can use my unix-like tail implementation.<br />1. it&#39;s free<br />2. it&#39;s easy to install (click-once)<br /><br />get it here whenever you need it: <br /><br />http://www.connexin.ch/cxntail<br /><br />cheers<br />ChristianChristianhttp://www.blogger.com/profile/13877515214652332296noreply@blogger.comtag:blogger.com,1999:blog-8942599.post-22284240611575533262008-12-29T12:11:00.000-05:002008-12-29T12:11:00.000-05:00Just an update...<BR/><BR/>I've got a post that demonstrates how to create excel friendly log4net output: <A HREF="http://stupiddumbguy.blogspot.com/2008/11/log4net-logparser-excel-output.html" REL="nofollow">Producing readable log4net output</A>bryanhttp://www.blogger.com/profile/01332614158223702009noreply@blogger.comtag:blogger.com,1999:blog-8942599.post-65784936561938306292008-10-23T04:02:00.000-04:002008-10-23T04:02:00.000-04:00did I spell 'witch' ?? :-)<BR/><BR/>Anyway, I'm using log4net quite extensively as well. In my current project, I have services oriented architecture and to monitor them I use the udp appender to one centralized viewer.<BR/>I tried at first 'Chainsaw', but I really didn't like the execution of it (it's java and requires to have an annoying console window, moreover the configuration of it wasn't so nice. Lately I found 'Log4View' and currently it works smoothly and suits my needs. The only problem that it's not free. It's kinda weird that the log4net library quite widely used, and there's no free worthy viewer!<BR/><BR/>anyway, thanks for your help, I'm gonna keep an eye on your posts :-)shlomikhttp://www.blogger.com/profile/12067353407061886467noreply@blogger.comtag:blogger.com,1999:blog-8942599.post-62140892278209794562008-10-22T23:02:00.000-04:002008-10-22T23:02:00.000-04:00Hmmm, good question. Oddly enough, now that I think of it, I can't claim that I have a favorite tool for log4net! I think that's largely because of two reasons:<BR/><BR/>1. the framework is so extensible that I tailor my configuration to suit my project's needs. I've used smtp, udp, database, console, trace, event logs and rolling file appenders in some shape or form, either alone or in combination with one another. The type of project will also dictate logging requirements, ie console app versus Windows Service versus 20 load balanced web-servers...<BR/><BR/>2. my logging needs change at different stages of the project. During development, I pipe debug information to files and console windows mainly to see that the information is getting logged as expected (correct values, order, occurrence); During QA emphasis shifts to make sure logs contain meaningful data when errors occur; in Production, I want to be notified when problems occur via email, snmp, rss, etc.<BR/><BR/>Personally, I use Notepad++ for the majority of simple log file viewing. <BR/><BR/>The main challenge with file-based readers is how they deal with content that has line-breaks (Stack Traces, rtf, xml nodes, etc) -- this type of content often is interpreted as several rows instead of a single record. If you solve this problem, then any reader will do: Excel, LogParser, etc. Stay tuned, sounds like another blog post.bryanhttp://www.blogger.com/profile/01332614158223702009noreply@blogger.comtag:blogger.com,1999:blog-8942599.post-21914683836957179582008-10-22T11:20:00.000-04:002008-10-22T11:20:00.000-04:00if you use log4net so often, I was wondering with witch viewer do you use?shlomikhttp://www.blogger.com/profile/12067353407061886467noreply@blogger.com