http://www.l4ndash.comRSS feeds for Log4Net Dashboard / Log4Net Viewer60http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/6/Logging-tutorials.aspx#Comments0http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=6http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/6/Logging-tutorials.aspxJim Christopher has written several excellent tutorials about log4net, and he promise to write more! http://www.beefycode.com/?tag=/log4netGeorg JansenMon, 15 Sep 2008 13:29:00 GMTf1397696-738c-4295-afcd-943feb885714:6http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/12/Log4Net-1210-is-released.aspx#Comments0http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=12http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=12&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/12/Log4Net-1210-is-released.aspxFinally Log4Net is no longer in beta, version 1.2.10 is released.A lot of people have been waiting for a “non-beta” version of log4net. Even though, version 1.2.9 have been around for quiet a while, and for most users, have proven to be more stable than a lot of commercial production releases. The complete release notes can be found on: http://logging.apache.org/log4net/release/release-notes.html Georg JansenWed, 26 Apr 2006 13:54:00 GMTf1397696-738c-4295-afcd-943feb885714:12http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/17/Programmatically-changing-log-file-names-in-Log4net.aspx#Comments16http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=17http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=17&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/17/Programmatically-changing-log-file-names-in-Log4net.aspxI needed to be able to change the file log4net was logging on programmatically, on the same time I wanted to use the other configuration options available in the config file. After several different approaches I ended up with writing a method like the one listed below: static bool ChangeLogFileName(string AppenderName, string NewFilename) { log4net.Repository.ILoggerRepository RootRep; RootRep = log4net.LogManager.GetRepository(); foreach (log4net.Appender.IAppender iApp in RootRep.GetAppenders()) { if (iApp.Name.CompareTo(AppenderName) == 0 && iApp is log4net.Appender.FileAppender) { log4net.Appender.FileAppender fApp = (log4net.Appender.FileAppender)iApp; fApp.File = NewFilename; fApp.ActivateOptions(); return true; // Appender found and name changed to NewFilename } } return false; // appender not found } The method basically search through all appenders to find the appender named in the input parameter. When an appender with the right name is found, it check if the appender is a FileAppender (or to be more precise, that the object found, implement the IFileAppender interface). I anyone know a more efficient way to find a named appender, I would very much like to know about it. I found out that using a standard configuration section in the config file failed if the filename was missing, and if a filename was stated that file would be created during the normal configuration (log4net.Config.XmlConfigurator.Configure()), therefore I ended up using the nul device as the filename. My config section is listed below: <appender name="FileAppender" type="log4net.Appender.FileAppender"> <param name="File" value="nul"/> <appendToFile value="true"/> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date [%thread] %-5level %logger - %message%newline"/> layout> appender> Since the RollingFileAppender inherits the FileAppender, the same method will also work with the RollingFileAppender. Using the nul device, causes the RollingFileAppender to issue some internal error messages during configuration (you will be able to see they if you turn on internal log4net debug). A small sidenote on the nul device. The nul device or the “nul” filename has been around in Windows and Dos since the beginning of time, at least since Dos 2.0. I believe it is inherited from the unix operating system. If you try to write to a file named nul, the content you write to the file will simply disappear. You can try it out with Notepad, save a file on c:\nul.txt, you will be warned that the file already exists, but you will be able to save to it. But you will never be able to retrieve anything (WROM Write only memory). Georg JansenTue, 24 Jan 2006 15:03:00 GMTf1397696-738c-4295-afcd-943feb885714:17http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/22/Log4Net-Mail-archive-available-on-wwwl4ndashcom.aspx#Comments0http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=22http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=22&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/22/Log4Net-Mail-archive-available-on-wwwl4ndashcom.aspxWhen it comes to Log4Net, it is one definitive source of information, and that is the log4net mailing list (log4net-user@logging.apache.org). I have made a copy of the Log4Net Mail available on http://www.l4ndash.com, and can be viewed as a forum on: http://www.l4ndash.com/Log4NetMailArchive/tabid/70/view/topics/forumid/1/Default.aspx. The mail archive is also available trough RSS: http://www.l4ndash.com/desktopmodules/ntforums/rss.aspx?portalid=0&forumid=1&tabid=70&moduleid=426 And I have a RSS which gives only the latest additions: http://www.l4ndash.com/desktopmodules/activeforumstopposts/rss.aspx?tabid=36&moduleid=427 My intentions is to update the mail archive every day, making it more up to date than the other available mail archives. From time to time the Log4Net developer mailing list (log4net-dev@logging.apache.org) contain threads which also is of interest to ordinary users, I will therefore also include some threads from this mailing list, making this mail archive a complete reference for the log4net community. Georg JansenTue, 29 Nov 2005 15:09:00 GMTf1397696-738c-4295-afcd-943feb885714:22http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/23/Lossy-logging-in-Log4Net.aspx#Comments0http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=23http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=23&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/23/Lossy-logging-in-Log4Net.aspxOne of the more exotic and advanced features of Log4net is lossy logging.   Actually the idea behind it is simply great, it supports the typical production scenario of: As long as everything is working, I don’t want my log filled up with debug (or info) messages, but when an error occurs, I would like to have all the messages that leads to this error situation.   And that’s what lossy logging is all about!   Implementing lossy logging is done through configuration, and as always in Log4net, configuration takes place in the configuration file, i.e. you don’t have to change your program.   To configure an appender to implement lossy logging, you need to write the following configuration statements in the config file:   <lossy value="true" />   <bufferSize value="10" />   <evaluator type="log4net.Core.LevelEvaluator">   <threshold value="ERROR"/>   evaluator>   Translated, this means: Log the last 10 messages every time an error (or fatal) message is encountered.   Lossy logging is supported by the appenders which are based on the BufferingAppenderSkeleton, currently that is AdoNetAppender, RemotingAppender, SmtpAppender, SmtpPickupDirAppender or BufferingForwardingAppender. If you are using another appender, you need a detour to the BufferingForwardingAppender, and have the BufferingForwardingAppender deliver the log rows to your appender of choice.   I wrote a small test program enclosed below:   using System;   using System.Text;       [assembly: log4net.Config.XmlConfigurator(Watch = true)]     namespace L4NTest   {   class Program   {   private static readonly log4net.ILog log   = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);       static void Main(string[] args)   {   TestLossy();   }       static void TestLossy()   {   int logno = 0;       for (int i = 0; i < 20; i++)   log.Debug("Log message no: " + (++logno).ToString());       log.Error("Error message no: " + (++logno).ToString());       for (int i = 0; i < 10; i++)   log.Debug("Log message no: " + (++logno).ToString());   }   }   }     This test program writes 31 log rows, first 20 debug rows, one error row and then 10 debug rows.   To test this I used two appenders, one FileAppender and on AdoNetAppender. The FileAppender was not configured to be lossy (in fact the FileAppender does not support Lossy), the AdoNetAppender was configured to be lossy and to log 10 rows if an Error occurred.   The complete configuration file for my test program is listed below:   xml version="1.0" encoding="utf-8" ?>   <configuration>   <configSections>   <section name="log4net" type="System.Configuration.IgnoreSectionHandler"/>   </configSections>       <appSettings>   <add key="log4net.Internal.Debug" value="true"/>   appSettings>       <log4net>   <appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">     <connectionType value="System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>   <connectionString value="Data Source=(Local); initial Catalog=Log4Net;Integrated Security=True;"/>   <commandText value="INSERT INTO Log4Net ([Date],[Thread],[Level],[Logger],[Message],[Exception]) VALUES (@log_date, @thread, @log_level, @logger, @message, @exception)"/>     <lossy value="true" />   <bufferSize value="10" />   <evaluator type="log4net.Core.LevelEvaluator">   <threshold value="ERROR"/>   evaluator>     <parameter>   <parameterName value="@log_date"/>   <dbType value="DateTime"/>   <layout type="log4net.Layout.RawTimeStampLayout"/>   parameter>   <parameter>   <parameterName value="@thread"/>   <dbType value="String"/>   <size value="255"/>   <layout type="log4net.Layout.PatternLayout">   <conversionPattern value="%thread"/>   layout>   parameter>   <parameter>   <parameterName value="@log_level"/>   <dbType value="String"/>   <size value="50"/>   <layout type="log4net.Layout.PatternLayout">   <conversionPattern value="%level"/>   layout>   parameter>   <parameter>   <parameterName value="@logger"/>   <dbType value="String"/>   <size value="255"/>   <layout type="log4net.Layout.PatternLayout">   <conversionPattern value="%logger"/>   layout>   parameter>   <parameter>   <parameterName value="@message"/>   <dbType value="String"/>   <size value="4000"/>   <layout type="log4net.Layout.PatternLayout">   <conversionPattern value="%message"/>   layout>   parameter>   <parameter>   <parameterName value="@exception"/>   <dbType value="String"/>   <size value="2000"/>   <layout type="log4net.Layout.ExceptionLayout"/>   parameter>   appender>     <appender name="FileAppender" type="log4net.Appender.FileAppender">   <file value="L4NTest.Log.Txt"/>   <appendToFile value="true"/>   <layout type="log4net.Layout.PatternLayout">   <conversionPattern value="%date [%thread] %-5level %logger [%ndc] - %message%newline"/>   layout>   appender>     <root>   <level value="ALL"/>   <appender-ref ref="AdoNetAppender"/>   <appender-ref ref="FileAppender"/>   root>     log4net>     configuration>   When running the program, the FileAppender wrote these log rows to the log file:   2005-11-09 13:19:47,906 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 1   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 2   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 3   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 4   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 5   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 6   2005-11-09 13:19:48,000 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 7   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 8   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 9   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 10   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 11   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 12   2005-11-09 13:19:48,015 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 13   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 14   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 15   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 16   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 17   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 18   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 19   2005-11-09 13:19:48,031 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 20   2005-11-09 13:19:48,046 [4988] ERROR L4NTest.Program [(null)] - Error message no: 21   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 22   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 23   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 24   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 25   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 26   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 27   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 28   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 29   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 30   2005-11-09 13:19:48,093 [4988] DEBUG L4NTest.Program [(null)] - Log message no: 31     The AdoNetAppender wrote these log rows to the database:     Date Level Logger Message 2005-11-09 13:19:48.017 DEBUG L4NTest.Program Log message no: 12 2005-11-09 13:19:48.017 DEBUG L4NTest.Program Log message no: 13 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 14 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 15 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 16 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 17 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 18 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 19 2005-11-09 13:19:48.030 DEBUG L4NTest.Program Log message no: 20 2005-11-09 13:19:48.047 ERROR L4NTest.Program Error message no: 21   As you can see, the AdoNetAppender has logged the errormessage, and the 9 rows before the error message, in contrast to the FileAppender which logs all messages.     Georg JansenSun, 13 Nov 2005 15:11:00 GMTf1397696-738c-4295-afcd-943feb885714:23http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/3/Fast-track-to-Log4Net-database-logging.aspx#Comments4http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=3http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/3/Fast-track-to-Log4Net-database-logging.aspxIn this article I will walk you trough the steps necessary to install, configure and getting started with Log4net, and writing log rows to Microsoft Sql Server using the AdoNetAppender. Georg JansenSat, 15 Oct 2005 18:11:00 GMTf1397696-738c-4295-afcd-943feb885714:3http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/1/Tracking-user-sessions-in-ASPNET-applications-using-Log4Net.aspx#Comments1http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=1http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/1/Tracking-user-sessions-in-ASPNET-applications-using-Log4Net.aspxWhen debugging web applications, with several clients making request at the (almost) same time, we need some way of distinguish and identify the different requests and sessions. Georg JansenSat, 08 Oct 2005 21:27:00 GMTf1397696-738c-4295-afcd-943feb885714:1http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/5/Using-Log4Net-to-log-from-Database-Stored-procedures.aspx#Comments2http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=5http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/5/Using-Log4Net-to-log-from-Database-Stored-procedures.aspxOne of the advantages of storing Log4Net log in a database using the AdoNetAppender, is the possibility to store log events from Stored Procedures in the same log.Georg JansenWed, 28 Sep 2005 15:19:00 GMTf1397696-738c-4295-afcd-943feb885714:5http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/2/Why-use-database-as-the-preferred-storage-of-logs.aspx#Comments0http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=69&ModuleID=413&ArticleID=2http://www.l4ndash.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2&PortalID=0&TabID=69http://www.l4ndash.com/News/tabid/69/ctl/ArticleView/mid/413/articleId/2/Why-use-database-as-the-preferred-storage-of-logs.aspxLog4Net gives us a collection of log appenders making it possible to choose where we writs logs. One of the possible appenders is the AdoNetAppender which write log-rows to a database. Georg JansenTue, 27 Sep 2005 18:06:00 GMTf1397696-738c-4295-afcd-943feb885714:2