Caveat: I haven’t actually used log4net. But if I understand correctly, the configuration is an XML file, isn’t it? And the pattern is just text with some special tokens. So have you tried embedding actual tab characters in your pattern? The XML sequence for a tab is 	, e.g.: <conversionPattern value=”%utcdate	[%thread]	%-5level	%logger	%message%newline” /> Or if you’re … Read more
You can add any properties you want to the GlobalContext. I use this context to store the process id, like this: log4net.GlobalContext.Properties[“pid”] = Process.GetCurrentProcess().Id; Then you reference this property from your appender using a regular pattern, like this: <layout type=”log4net.Layout.PatternLayout”> <conversionPattern value=”%date %property{pid} %level %logger – %message%newline” /> </layout> You can add as many properties … Read more
I also have trouble with this method of boostrapping log4net. The documentation says you have to make a call very early in your application startup if you use configuration attributes you must invoke log4net to allow it to read the attributes. A simple call to LogManager.GetLogger will cause the attributes on the calling assembly to … Read more
Log4Net will fail silently if something goes wrong and it is unable to write to its appenders. This is actually a good thing, since it means a bit of failed logging won’t bring down an otherwise healthy system, but it can be annoying when something isn’t logging as you expect. Your best bet is to … Read more
Give the following code in your application before you put your logging code: log4net.Config.XmlConfigurator.Configure(); You can define it in Global.asax: void Application_Start(object sender, EventArgs e) { // Code that runs on application startup // Initialize log4net. log4net.Config.XmlConfigurator.Configure(); } You can also add the following line as Kevin advised (either mentioning your config file name or … Read more
I assume that the application should create only one log file every time it runs, so you do not need a rolling file appender (though my solution would apply for rolling file appenders as well): <appender name=”FileAppender” type=”log4net.Appender.FileAppender”> <file type=”log4net.Util.PatternString” value=”c:\temp\App-%date{yyyy-MM-dd_HH-mm-ss}.log” /> <appendToFile value=”true” /> <layout type=”log4net.Layout.PatternLayout”> <conversionPattern value=”%date [%2thread] %-5level – %message%newline” /> </layout> … Read more
Assuming you’re using log4net out of the box, you can dig your way down & flush the appender like this: public void FlushBuffers() { ILog log = LogManager.GetLogger(“whatever”); var logger = log.Logger as Logger; if (logger != null) { foreach (IAppender appender in logger.Appenders) { var buffered = appender as BufferingAppenderSkeleton; if (buffered != null) … Read more
Within the definition of the appender, I believe you can do something like this: <appender name=”AdoNetAppender” type=”log4net.Appender.AdoNetAppender”> <filter type=”log4net.Filter.LevelRangeFilter”> <param name=”LevelMin” value=”INFO”/> <param name=”LevelMax” value=”INFO”/> </filter> … </appender>
The other answers escape the “g” in “log” since “g” is a special character in datePattern. This isn’t wrong, but I prefer to wrap the entire set of non-date characters in single quotes, like so: <datePattern value=”yyyy-MM-dd’.log'” /> This gives the same results, but is easier for me to manage. This way, I don’t have … Read more
I think you’ve got the reason. I do it that way so I don’t have to worry about the class name and can just copy and paste boiler plate code in a new class. For the official answer, see: How do I get the fully-qualified name of a class in a static block? at the … Read more