Skip to content
Minimalistic viewer for NLog, Log4Net and others.
C# PowerShell XSLT Shell
Find file
Latest commit e77a77f Sep 30, 2013 @SHSE Updated NuGet


Minimalistic viewer for NLog, Log4Net and others.

or download binaries

LogWatch allows you to view output from NLog and Log4Net loggers.


  • Designed to handle large log files (hundreds of megabytes, it doesn't read all the data into memory)
  • Live file streaming support (view files that are currently being updated by the logger)
  • Built-in support for CSV and Log4J XML formats
  • Automatic log format selection
  • Receives log records via network
  • Provides quick jump to a next Trace/Debug/Info/Warn/Error/Fatal record functionality
  • Search using simple text search or regular expressions (press Ctrol+F to activate)
  • Ability to define custom log parser using Lex syntax


LogWatch has built-in support for the following log sources:

  • File source
  • UDP source

When using file source LogWatch sets a monitor on the file and provides live updates on the records.


The application supports the following log formats out of the box:

LogWatch automatically determines format of the source.

CSV delimeter can be ; or ,. The log file must have header with some of the following feillds (case sensitive):


Here is an example configuration of CSV layout for NLog:

<target name="file" xsi:type="File" encoding="utf-8" fileName="mylog.log">
  <layout xsi:type="CsvLayout">
    <column name="time" layout="${longdate}" />
    <column name="message" layout="${message}" />
    <column name="logger" layout="${logger}" />
    <column name="level" layout="${level}" />
    <column name="exception" layout="${exception:format=ToString}" />

Log4J XML is the default format for NLogViewer. Here is an example configuration for NLog:

<target name="viewer" xsi:type="NLogViewer" address="udp://" includeNLogData="true">
  <parameter name="exception" layout="${exception:format=ToString}"/>

NLogViewer sends records via UDP in Log4J XML format.


  • documentation
  • custom log record properties
Something went wrong with that request. Please try again.