There is a third-party log4net adapter for the ASP.NET Core logging interface. Only thing you need to do is pass the ILoggerFactory to your Startup class, then call loggerFactory.AddLog4Net(); and have a config in place. So you don’t have to write any boiler-plate code. More info here
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>
You are getting duplicated because you are telling it to log messages twice. I wouldn’t recommend using additivity here since you might experience some side effects, simply remove unnecessary configuration: <root> <level value=”WARN” /> <appender-ref ref=”Console” /> <appender-ref ref=”LogFile” /> </root> <logger name=”myprogram”> <level value=”INFO” /> </logger> You don’t need to indicate the appender-ref in … Read more
You need to call the Configurefunction of the XmlConfigurator log4net.Config.XmlConfigurator.Configure(); Either call before your first loggin call or in your Global.asax like this: protected void Application_Start(Object sender, EventArgs e) { log4net.Config.XmlConfigurator.Configure(); }
Sure, use a filter. Here’s the snippet posted on the blog, for future reference – all credit to the author of that blog post: <filter type=”log4net.Filter.LoggerMatchFilter”> <!– allows this sub-namespace to be logged… –> <loggerToMatch value=”Noisy.Namespace.But.Important” /> </filter> <filter type=”log4net.Filter.LoggerMatchFilter”> <!– …but not the rest of it –> <loggerToMatch value=”Noisy.Namespace” /> <acceptOnMatch value=”false” /> </filter>
You need to have both appenders declared in your <root> section. Configure your log4net like this: <log4net> <appender name=”Console” type=”log4net.Appender.ConsoleAppender”> <layout type=”log4net.Layout.PatternLayout”> <conversionPattern value=”%date %-5level: %message%newline” /> </layout> </appender> <appender name=”RollingFileAppender” type=”log4net.Appender.RollingFileAppender”> <file value=”Log.txt” /> <appendToFile value=”false” /> <rollingStyle value=”Size” /> <maxSizeRollBackups value=”10″ /> <maximumFileSize value=”50MB” /> <staticLogFileName value=”true” /> <layout type=”log4net.Layout.PatternLayout”> <conversionPattern value=”%date %-5level[%logger]: … Read more
In the very early days (.NET 1.0) tracing in the .NET Framework was pretty limited. For example TraceSource partitioning didn’t come until .NET 2.0 and you only had four levels (Error, Warning, Information, Verbose), although you could use half a dozen boolean switches for partitioning if you wanted. log4j is popular in Java and so … Read more
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
DailyRollingFileAppender is what you exactly searching for. <appender name=”roll” class=”org.apache.log4j.DailyRollingFileAppender”> <param name=”File” value=”application.log” /> <param name=”DatePattern” value=”.yyyy-MM-dd” /> <layout class=”org.apache.log4j.PatternLayout”> <param name=”ConversionPattern” value=”%d{yyyy-MMM-dd HH:mm:ss,SSS} [%t] %c %x%n %-5p %m%n”/> </layout> </appender>
Solution is quite easy in your situation; just use this code: var rootAppender = ((Hierarchy)LogManager.GetRepository()) .Root.Appenders.OfType<FileAppender>() .FirstOrDefault(); string filename = rootAppender != null ? rootAppender.File : string.Empty;