Simple Logging Façade

New Post: thread safety

PerrySharePoint — Thu, 09 May 2013 18:10:31 GMT

Is SLF thread-safe? If not, how does one use it safely from multiple threads potentially simultaneously?

New Post: How about .NET Framework support

sgryphon — Fri, 19 Apr 2013 14:03:00 GMT

Um, hello?

For a .NET facade, it's pretty strange that you seem to support a bunch of third party logging frameworks, but not the .NET Framework itself, i.e. System.Diagnostics, TraceSource, etc.

New Post: Releasing File Lock

benhelite — Fri, 15 Feb 2013 22:18:37 GMT

Hello everyone,

I have a program which uses SLF for logging. This program runs 24/7 and I would like to upload the log files to a remote server every night for later review.

My question is, how do I release the file lock for the log without closing the program?

I was hoping to suspend logging, upload the logs, either delete the log file or erase the contents, and then resume logging.

ILogger logger = LoggerService.GetLogger(typeof(TaskScheduler).FullName);

// Other initialization here

foreach (var task in managedTasks.OrderBy(t => t.Priority))
{
    if (task.NextRunTime <= DateTime.Now)
    {
        dataManager.CurrentStatus = AppStatus.Running;
        if (task.Name == "Log Sender")
        {
             logger = null;
        }

        // Run the task

        if (task.Name == "Log Sender")
            logger = LoggerService.GetLogger(typeof(TaskScheduler).FullName);

        dataManager.CurrentStatus = AppStatus.Idle;
    }
}

Currently, when I do this, I'm still getting an IOException because the file is still locked by the Task Scheduler.

Any ideas are appreciated.

Ben

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

Commented Issue: Create NuGet package for SLF [31452]

ipashchuk — Wed, 14 Sep 2011 18:15:03 GMT

Would be great to have a NuGet package so that the SLF.dll wouldn't have to be embedded in libraries that are distributed as NuGet packages.
Comments: ** Comment from web user: ipashchuk **

I'm attaching a NuGet package for SLF Core. I would be happy to upload it to the official NuGet repository if you guys are busy.

Commented Issue: Create NuGet package for SLF [31452]

ipashchuk — Tue, 13 Sep 2011 14:08:58 GMT

Would be great to have a NuGet package so that the SLF.dll wouldn't have to be embedded in libraries that are distributed as NuGet packages.
Comments: ** Comment from web user: ipashchuk **

It would probably be best to create NuGet packages as follows:
- SimpleLoggingFacade.Core (just the SLF binary)
- SimpleLoggingFacade.Log4Net
- SimpleLoggingFacade.NLog
- SimpleLoggingFacade.EntLibLogging
- SimpleLoggingFacade.BitFactory

Created Issue: Create NuGet package for SLF [31452]

ipashchuk — Tue, 13 Sep 2011 13:59:54 GMT

Would be great to have a NuGet package so that the SLF.dll wouldn't have to be embedded in libraries that are distributed as NuGet packages.

Reviewed: SLF 1.0.0 December 2009 (Sep 13, 2011)

ipashchuk — Tue, 13 Sep 2011 13:56:23 GMT

Rated 4 Stars (out of 5) - Great library. Would be nice to have a NuGet package...

New Post: Factory for BitLaboratory (Object Guy's) Logging Framework?

benmcclure — Sun, 27 Mar 2011 07:26:02 GMT

This is an old message, but I have the exact same issue...

BitFactory can be configured declaratively, and SLF can be configured declaratively, but it does not seem they can be configured declaratively together without a factory for creating BitFactoryLogger objects...

Unless I am missing something as well.

New Post: callsite is lost through NLogFacade

Mixmasterxp — Wed, 16 Feb 2011 04:11:53 GMT

Have this been fixed for NLog? Instead of importing the NLogFacade dll, I copied the 2 files into my project. Would this prevent callsite from working?

I set up logger in my global.ascx file as follows:

  //Setup logger
  LoggerService.FactoryResolver = new SimpleFactoryResolver(new NLogLoggerFactory());

Later down in my app, I log like this:

ILogger logger = LoggerService.GetLogger();
logger.Error("Exception: {0}", ex.Source);

My NLog.onfig:

<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <targets>
    <target name="file" xsi:type="AsyncWrapper" queueLimit="5000" overflowAction="Discard">
      <target name="FileError"
            xsi:type="File"
            fileName="${basedir}/App_Data/Logs/errors.txt"
            archiveFileName="${basedir}/App_Data/Archives/log.{#####}.txt"
            archiveAboveSize="10240"
            archiveNumbering="Sequence"
            concurrentWrites="true"
            keepFileOpen="false"
            encoding="iso-8859-2"
            layout="${longdate}|${callsite:className=true:fileName=false:includeSourcePath=false:methodName=true}|${message}"/>
      <target name="FileInfo" xsi:type="File" fileName="${basedir}/App_Data/Logs/info.txt"/>
    </target>
  </targets>
  <rules>
    <logger name="*" level="Error" writeTo="FileError"/>
    <logger name="*" level="Info" writeTo="FileInfo"/>
  </rules>
</nlog>

New Post: Using NLog.config

Mixmasterxp — Mon, 14 Feb 2011 00:56:19 GMT

Stupid question lol. Delete pls.

New Post: Reload configuration for configuration file on fly

wageoghe — Wed, 10 Nov 2010 22:23:44 GMT

You might also consider using Common.Logging. It supports (via the config file) telling log4net to configure and watch. It also supports putting the log4net configuration in the app.config file OR in a separate config file.

New Post: Reload configuration for configuration file on fly

alfrye — Mon, 08 Nov 2010 21:31:36 GMT

I am looking at using SLF and log4net as the logging framework on one of my projects. I am setting up the SLF and log4net configuration in my app,config file and everything loads and logs as excepted. However one of my requirements is to be able to change the log4net properties from my application and have the logger to use the new settings without reloading the application. In the past I have used the log4net xmlconfiguration configandwatch() method.

Is there a way to handle this through the SLF framework.

New Post: SLF with Windows Phone?

BeauGeek — Mon, 04 Oct 2010 18:23:38 GMT

Is SLF (or a future version) usable with Windows Phone 7?

Thanks.

Vikram

Commented Task: Explore the impact of SLF on nlog / log4net stacktraces [25524]

wageoghe — Fri, 10 Sep 2010 18:31:18 GMT

Both NLog and log4net have formatters that output information relating to the call-stack. Currently SLF will obscure this.

What can we do?

The only solution I can thin of, which is a bit nasty, is to create our own builds of NLog and log4net that skip stack frames.
Comments: ** Comment from web user: wageoghe **

I have added a comment in the "callsite is lost through the NLogFacade" discussion thread about how to fix this problem for log4net. You can look there for more info, or I will also include some sample code here:

/// <summary>
/// Sends the message to the underlying log4net system.
/// </summary>
/// <param name="logLevel">the level of this log event.</param>
/// <param name="message">the message to log</param>
/// <param name="exception">the exception to log (may be null)</param>
protected override void WriteInternal(LogLevel logLevel, object message, Exception exception)
{
Level level = GetLevel(logLevel);
_logger.Log(declaringType, level, message, exception);
}

By using the log4net logger's "Log" method and passing the type of the wrapping logger, log4net knows which DeclaringType in the call stack is the entry point for the logging call. One step up from that should be in the actual user code.

New Post: callsite is lost through NLogFacade

wageoghe — Fri, 10 Sep 2010 18:19:05 GMT

Building on my last comment, here is some code from Common.Logging that I think is showing the correct technique for preserving the code location. Note that declaringType is stored in the wrapping logger (in this case Common.Logging's Log4netLogger) and it is the type of their Log4netLogger (as compared to the use of the logger's base class that is used to make NLog's code location work correctly).

        /// <summary>
        /// Sends the message to the underlying log4net system.
        /// </summary>
        /// <param name="logLevel">the level of this log event.</param>
        /// <param name="message">the message to log</param>
        /// <param name="exception">the exception to log (may be null)</param>
        protected override void WriteInternal(LogLevel logLevel, object message, Exception exception)
        {
            Level level = GetLevel(logLevel);
            _logger.Log(declaringType, level, message, exception);
        }

New Post: Adding unique IDs to log messages

wageoghe — Fri, 10 Sep 2010 18:11:13 GMT

You can go to the log4net source repository here to find a log4net extension that shows how to extend log4net to include an event id parameter. Essentially they define an interface that is the same as (or similar to) ILog, with an additional eventId parameter. The implementation wraps a regular log4net logger. Each logging call creates a log4net LoggingEvent structure/class and adds an "EventID" property to the LoggingEvent's Properties dictionary. It then uses the regular log4net logger's Log method (which takes a LoggingEvent sturcture/class). To get the EventID to show up in the output, I guess you would just have to add the appropriate properties reference in the format string.

If SLF wanted to support the ability to log "event id" natively, one approach might be to declare an interface that is parallel to SLF.ILogger. It might be SLF.IEventIdLogger. It would have the same parameters as ILogger, with the addition of an event id, maybe as the first parameter like log4net did. Now, if someone wants to log event ids, they would request IEventIdLoggers (maybe you would need a parallel LogManager like log4net implemented in their extension) and log away. A similar technique could probably be used for NLog (put the EventId in the appropriate NLog context dictionary).

New Post: Expose logging context

wageoghe — Wed, 08 Sep 2010 21:05:39 GMT

Should slf "generically" expose the logging context (NDC, MDC, etc) of log4net and NLog?

For an example of a logging abstraction that does this, see the log4net and NLog abstractions at the Castle project. log4net and NLog loggers can be resolved as basic loggers (I think with an ILogger interface) or as "extended" loggers (IExtendedLogger). From what I can tell, the extended logger interface exposes all of the "context" information (stacks and dictionaries) that can be exposed on log4net and NLog. There is also a TraceSource based logger, but it is only exposed as ILogger. I'm not sure what would happen if you tried to access the extended information on a TraceSource based logger, maybe an exception, maybe it just doesn't support an interface.

Anyway, without exposing the logging context generically, one would have to resort to referencing the specific logging platform's LogManager to set the context, thus defeating the purpose of using the abstraction.

Of course, there is the inherent conflict between limiting the facade to capabilities available in all logging platforms vs implementing/exposing capabilities that are available in some, but not all, logging platforms.

New Post: using external config file with slf

vmlf — Sat, 28 Aug 2010 16:19:37 GMT

Due to the length and complexity of some log config files, it would be usefull if we could store it in an external file and have some way to point SLF to load it from there instead of the app config file.