1. Documentation
  2. KissLog SDK
  3. Logs output

Logs output

KissLog saves the logs to multiple output locations by using log listeners.

Log listeners are registered at application startup using the KissLogConfiguration.Listeners container.

using KissLog;

namespace MyApplication
{
    public class MvcApplication : System.Web.HttpApplication
    {
        private void RegisterKissLogListeners()
        {
            KissLogConfiguration.Listeners.Add(new RequestLogsApiListener());
            KissLogConfiguration.Listeners.Add(new LocalTextFileListener()));
        }
    }
}

kisslog.net

RequestLogsApiListener saves the logs to kisslog.net (or KissLog on-premises).

kisslog.net output 
using KissLog;
using KissLog.CloudListeners.Auth;
using KissLog.CloudListeners.RequestLogsListener;

namespace MyApplication
{
    public class MvcApplication : System.Web.HttpApplication
    {
        // [...]

        private void RegisterKissLogListeners()
        {
            KissLogConfiguration.Listeners.Add(new RequestLogsApiListener(new Application("0337cd29-a56e-42c1-a48a-e900f3116aa8", "35f66045-16df-4a3a-9cb4-b1762b464348"))
            {
                ApiUrl = "https://api.kisslog.net"
            });
        }
    }
}

Local text files

LocalTextFileListener saves the logs on local text files.

Local text files output 
using KissLog;

namespace MyApplication
{
    public class MvcApplication : System.Web.HttpApplication
    {
        // [...]

        private void RegisterKissLogListeners()
        {
            KissLogConfiguration.Listeners.Add(new LocalTextFileListener(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "Logs"))
            {
                FlushTrigger = FlushTrigger.OnMessage
            });
        }
    }
}

NLog

NLogTargetListener saves the logs created with KissLog.ILogger to all the NLog targets defined in NLog.config.

This is useful when you want to use save the logs to both kisslog.net and NLog text-files.

NLog output
NLog.config 
using KissLog;

namespace MyApplication
{
    public class MvcApplication : System.Web.HttpApplication
    {
        // [...]

        private void RegisterKissLogListeners()
        {
            KissLogConfiguration.Listeners.Add(new NLogTargetListener());
        }
    }
}

Custom listeners

Custom log listeners can be created by implementing the ILogListener interface.

DebugOutputListener.cs
public class DebugOutputListener : ILogListener
{
    public int MinimumResponseHttpStatusCode { get; set; } = 0;
    public LogLevel MinimumLogMessageLevel { get; set; } = LogLevel.Trace;
    public LogListenerParser Parser { get; set; } = new LogListenerParser();

    public void OnBeginRequest(HttpRequest httpRequest, ILogger logger)
    {
        string text = string.Format(">>>>>> {0} {1}", httpRequest.HttpMethod, httpRequest.Url.PathAndQuery);

        Debug.WriteLine(text);
    }

    public void OnMessage(LogMessage message, ILogger logger)
    {
        string text = string.Format(">>>>>> {0} {1}", message.LogLevel, message.Message);

        Debug.WriteLine(text);
    }

    public void OnFlush(FlushLogArgs args, ILogger logger)
    {
        HttpRequest request = args.WebProperties.Request;
        HttpResponse response = args.WebProperties.Response;

        int httpStatusCode = (int)response.HttpStatusCode;

        string text = string.Format(">>>>>> Completed {0}", httpStatusCode);

        Debug.WriteLine(text);
    }
}

using KissLog;

namespace MyApplication
{
    public class MvcApplication : System.Web.HttpApplication
    {
        // [...]

        private void RegisterKissLogListeners()
        {
            KissLogConfiguration.Listeners.Add(new DebugOutputListener());
        }
    }
}
DebugOutputListener output

Another custom log listener can be found on the Custom MongoDB listener example.