YALV! - Yet Another Log4Net Viewer

Updated Release: YALV! v1.4.0.0

dmitriy_konovalov — Mon, 20 May 2013 16:50:02 GMT

"log4j" file extension support
Ability to filter files by name when reading folder
NLog-specific properties support
Logger hierarchy tree filter

Updated Release: YALV! v1.4.0.0

dmitriy_konovalov — Mon, 20 May 2013 16:47:32 GMT

Log4J extension support
Regex filter condition in Favorites for each folder
NLog-specific properties support
Logger hierarchy tree filter

Updated Wiki: Home

dmitriy_konovalov — Sun, 19 May 2013 18:44:04 GMT

Project Description

YALV! is a log file viewer for Log4Net with handy features like log merging, filtering, open most recently used files, items sorting and so on. It is easy to use, it requires no configuration, it has intuitive and user-frienly interface and avaliable in several languages. It is a WPF Application based on .NET Framework 4.0 and written in C# language.

[More Screenshots]

Main features:

Log files merging into one list
Dynamic log events filtering
Dynamic show/hide log events by log level
Favorites log folders list
Open most recently used files
Column sorting
Copy log event data to clipboard

Localizations

English
French
German
Italian
Russian
Japanese

Configuration

YALV itself does not require any setup, but log4net must be setup in your application to write XML content in XmlLayoutSchemaLog4j layout to log files. Read more...

Usage

Download latest binaries, unzip and launch YALV.exe. That's all!
YALV GUI language follows your Windows culture automatically, but you can override this behavior. Read more...

Feedback

We'd really appreciate your YALV experience and it would be great if you leave a feedback on current release (on the right).
If you have any suggestions, ideas or you found some bugs or translation inaccuracies, please feel free to create an issue.
Also there are already some issues pending. Please vote!

Created Feature: Add ability to filter files by name when reading folder [1615]

dmitriy_konovalov — Sun, 19 May 2013 18:41:57 GMT

# Idea
User should be able to define filter rule for a folder. This rule should be applied when loading files from folder. For example, it would be useful if I want to hide files without __log__ in filename.Or, if I'd like to hide log files with date on the end (in case of rolling file appender).

# Behavior
User should be able to define regex rule for each Favorite folder. This rule should be applied when file list is retrieved. This setting should be stored whith Favorites folders settings.

Created Feature: Create one complex Settings file [1614]

dmitriy_konovalov — Sun, 19 May 2013 18:28:46 GMT

# Idea
Merge __YalvFolders.xml__ into __YALV.exe.config__ to make one centralized settings file. This will be useful when some other parameters hill have to be saved.
Also, this file should be stored in shared folder with guaranteed write access, for example
> @AppData@\YALV\
User may not have righs to edit files in YALV runtime folder and in this case YALV will not be able to save settings.
Also storing settings in separate folder will allow painless upgrade for future versions with preserving settings untouched.

Created Feature: Add "log4j" extension suppord [1613]

dmitriy_konovalov — Sun, 19 May 2013 18:08:46 GMT

# Idea
Support for __log4j__ extension for log files should be added fo files with log4j xml layout. This will allow users to associate YALV to this file type and then open log files in one click.

Created Feature: Ability to show and hide columns in grid [1612]

dmitriy_konovalov — Sun, 19 May 2013 17:56:00 GMT

# Idea
Add ability to choose which colums in grid are visible and which are not.

# Behavior
New item "Customize columns..." should be added into View menu in Main window. Clicking on this item new dialog should be shown. In this new window user should be able to check/uncheck columns to show in grid.
Chosen columns should be saved in settings file between sessions.

Created Feature: Add logger hierarchy tree filter [1611]

dmitriy_konovalov — Sun, 19 May 2013 17:16:42 GMT

# Idea
New panel should be added to Main Window. This panel should contain a tree that represents a logger hierarchy. User will be able to analyze events faster and will be able to filter events in by logger just in sevetal mouse clicks.

# Behavior
That panel should contain a tree with checkboxes on every node. This tree should be populated by grouping all log events by logger field. Unchecking a node should hide events from appropriate logger and cheching node back should reveal them. Changing active row on grid should highlight appropriate logger in tree.

# Tree populating
Logger hierarchy should be built by splitting logger field by dot (".").

Closed Task: Split YALV into logical layers [1610]

dmitriy_konovalov — Sun, 19 May 2013 16:30:18 GMT

* Create YALV.Core project
* Move all gui-independent classes to YALV.Core
Comments: Completed in [changeset:23987]

Source code checked in, #23987

dmitriy_konovalov — Sun, 19 May 2013 16:20:44 GMT

Finished refactoring via extracting worker methods from GlobalHelper into YALV.Core.DataService. All exception are accurately rethrowed from YALV.Core layer to YALV GUI layer [workitem:1610] Credits block in About.xaml was updated with German translator name and contacts

Source code checked in, #23986

dmitriy_konovalov — Sun, 19 May 2013 15:02:48 GMT

Most of all gui-independent classes were moved to YALV.Core project [workitem:1610]

Source code checked in, #23985

dmitriy_konovalov — Sun, 19 May 2013 15:02:46 GMT

Most of all gui-independent classes were moved to YALV.Core project [workitem:1610]

Edited Task: Split YALV into logical layers [1610]

dmitriy_konovalov — Sun, 19 May 2013 14:59:13 GMT

* Create YALV.Core project
* Move all gui-independent classes to YALV.Core

Created Task: Split YALV into logical layers [1610]

dmitriy_konovalov — Sun, 19 May 2013 14:59:12 GMT

* Create YALV.Core project
* Move all gui-independent classes to YALV.Core

Source code checked in, #23981

dmitriy_konovalov — Sun, 19 May 2013 10:29:59 GMT

Log4net config examples updated in About.xaml.cs "de" and "fr" culture examples added to app.config Culture changed from specific "en-US" to general "en" in default Resources.resx

Updated Wiki: Documentation

dmitriy_konovalov — Sun, 19 May 2013 10:11:34 GMT

Configuring Log4Net

Log4Net must be setup to write XML content in XmlLayoutSchemaLog4j layout to log files. This configuration normally should be performed just once and it is quite simple. Just a few lines need to be added to your application config file (or log4net config file) to configure it to use this format.
We suggest you to create separate appender named FileXmlAppender to create log files in XmlLayoutSchemaLog4j layout. Your log4net section should look like this:

<log4net>
    <appender name="FileAppenderXml" type="log4net.Appender.FileAppender">
        <file type="log4net.Util.PatternString" value="sample-log.xml"/>
        <appendToFile value="true"/>        
        <layout type="log4net.Layout.XmlLayoutSchemaLog4j">
            <locationInfo value="true"/>
        </layout>
        <param name="Encoding" value="utf-8" /> 
    </appender>
    <!-- other appenders defined here -->

    <root>
        <level value="ALL" />
        <appender-ref ref="FileAppenderXml" />
        <!-- other appenders enabled here -->
    </root>
</log4net>

Overriding GUI language

By default, YALV GUI languade follows your Windows culture automatically. If no appropriate localization was found, then default "en" culture will be used.
If you want to override culture used by YALV, just specify desired culture code in "Culture" setting in YALV.exe.config file ("ja" for example):

<appSettings>
  <add key="Culture" value="ja" />
</appSettings>

If you want to enable default behavior, then just clear "Culture" setting and leave it empty:

<appSettings>
  <add key="Culture" value="" />
</appSettings>

Screenshots

Updated Wiki: Documentation

dmitriy_konovalov — Sun, 19 May 2013 10:11:16 GMT

Configuring Log4Net

<log4net>
    <appender name="FileAppenderXml" type="log4net.Appender.FileAppender">
        <file type="log4net.Util.PatternString" value="sample-log.xml"/>
        <appendToFile value="true"/>        
        <layout type="log4net.Layout.XmlLayoutSchemaLog4j">
            <locationInfo value="true"/>
        </layout>
        <param name="Encoding" value="utf-8" /> 
    </appender>
    <!-- other appenders defined here -->

    <root>
        <level value="ALL" />
        <appender-ref ref="FileAppenderXml" />
        <!-- other appenders enabled here -->
    </root>
</log4net> {code:xml}

! Overriding GUI language {anchor:OverridingGUILanguage}
By default, YALV GUI languade follows your Windows culture automatically. If no appropriate localization was found, then default "en" culture will be used.
If you want to override culture used by YALV, just specify desired culture code in "Culture" setting in *YALV.exe.config* file ("ja" for example):

If you want to enable default behavior, then just clear "Culture" setting and leave it empty:

<appSettings>
<add key="Culture" value="" />
</appSettings>{code:xml}

Screenshots

Updated Wiki: Documentation

dmitriy_konovalov — Sun, 19 May 2013 10:10:56 GMT

Configuring Log4Net

<log4net>
    <appender name="FileAppenderXml" type="log4net.Appender.FileAppender">
        <file type="log4net.Util.PatternString" value="sample-log.xml"/>
        <appendToFile value="true"/>        
        <layout type="log4net.Layout.XmlLayoutSchemaLog4j">
            <locationInfo value="true"/>
        </layout>
        <param name="Encoding" value="utf-8" /> 
    </appender>
    <!-- other appenders defined here -->

    <root>
        <level value="ALL" />
        <appender-ref ref="FileAppenderXml" />
        <!-- other appenders enabled here -->
    </root>
</log4net>{code:xml}

! Overriding GUI language {anchor:OverridingGUILanguage}
By default, YALV GUI languade follows your Windows culture automatically. If no appropriate localization was found, then default "en" culture will be used.
If you want to override culture used by YALV, just specify desired culture code in "Culture" setting in *YALV.exe.config* file ("ja" for example):

If you want to enable default behavior, then just clear "Culture" setting and leave it empty:

<appSettings>
<add key="Culture" value="" />
</appSettings>{code:xml}

Screenshots

Updated Wiki: Documentation

dmitriy_konovalov — Sun, 19 May 2013 10:07:12 GMT

Configuring Log4Net

<log4net>
    <appender name="FileAppenderXml" type="log4net.Appender.FileAppender">
        <file type="log4net.Util.PatternString" value="sample-log.xml"/>
        <appendToFile value="true"/>        
        <layout type="log4net.Layout.XmlLayoutSchemaLog4j">
            <locationInfo value="true"/>
        </layout>
        <param name="Encoding" value="utf-8" /> 
    </appender>
    <!-- other appenders defined here -->

    <root>
        <level value="ALL" />
        <appender-ref ref="FileAppenderXml" />
        <!-- other appenders enabled here -->
    </root>
</log4net>

Overriding GUI language

<appSettings>
  <add key="Culture" value="ja" />
</appSettings>

If you want to enable default behavior, then just clear "Culture" setting and leave it empty:

<appSettings>
  <add key="Culture" value="" />
</appSettings>

Screenshots

Updated Wiki: Home

dmitriy_konovalov — Sun, 19 May 2013 10:02:44 GMT

Project Description

Main features:

Log files merging into one list
Dynamic log events filtering
Dynamic show/hide log events by log level
Favorites log folders list
Open most recently used files
Column sorting
Copy log event data to clipboard

Localizations

English
French
German
Italian
Russian
Japanese

Configuration

YALV itself does not require any setup, but log4net must be setup in your application to write XML content in XmlLayoutSchemaLog4j layout to log files. Read more...

Usage

Download latest binaries, unzip and launch YALV.exe. That's all!
YALV GUI language follows your Windows culture automatically, but you can override this behavior. Read more...