Information

Downloads
 
  To keep the development going please check out what Diino has to offer.
 

A free (open source) log monitor / log viewer for:

  • Files and folders
  • Incomming UDP traffic
  • EventLogs
  • SQL- Server tables
  • Atom and RSS feeds
  • StdOut and StdErr

FEATURES:

Listens to a UDP port either in broadcast or single endpoint mode.

Monitors an eventlog, uses events on the local machine and polling on remote machines.

Monitors a log file or folder. Doing a tail using polling.

Monitors a table in a MS SQL-Server database. Doing a tail using polling.

Monitors Atom and RSS feeds.

Monitor StdOut and StdErr of an application.

Can highlight or hide messages depending on content.

Supports multiple simultaneous listeners in each session.

Supports several simultaneous sessions (MDI).

Requires the Microsoft .NET Framework 2.0

Main window Configuration 2 Configuration

1. Main window

1.1 New session

This is where you start a new session. See related topics and documents Configure

1.2 Clear

Clears the active window.

1.3 Pause

Stops the active viewer from showing new events. All new events are cached until the button is pressed again.

1.4 Actions

Manages the actions for the current viewer. Actions

1.5 Settings

Shows the session configuration dialog. Where you can add and remove listeners and actions from the current session. Configure

1.6 Sessions

Enables you to organize the open session windows.

1.7 Help

  • About: Will show a dialog with some application data.
  • Documentation: Opens the help file in your default web browser.
  • Check for updates: Will check online if there is a new version of the application available.
  • Register filetype: Associates the .l4n extension with logview4net so that you can doubleclick on a settings file to open the application.

1.7 Context menu

There is a context menu in each session window that has options tho quickly create actions based on selected text in the viewer.

2. Configure

This is where you configure a log session.

  • Session title: This is the window title of the session.
  • Listeners: Choose what kind of log listener you want to use in the drop down list and click 'Add'. You will be presented with the relevant options for the selected type of listener. You can add as many listeners to one session as you want as long as they are not in conflict with each other. This will for example happen if you try to add two UDP Listeners that listen on the same port.
  • Viewer: This is where you configure the viewer.
  • Load: Cick here to load a saved log session configuration.
  • Save: Click here to save the current log session configuration. If you save it as DefaultSession.xml in the application folder it will be loaded when starting the application.
  • OK: Click here to start the session.

2.1 Viewer

This is where all new log events are showed. You can change font and colors. Each viewer is associated with a set of actions. 'Buffer' set how many characters that are stored in the viewer. Old events are purged to make place for new ones once this number is reached.

2.2 Actions

Actions are instructions to the viewer how it should react to different events. When an event is received by the viewer it looks through the associated actions from the top and applies the first matching action. An action is concidered a match when its pattern matches one or more words in the log event.

  • Pattern: A string to match against the text of an event
  • Action type: What to do when an event matches the pattern.
  • Color: The fore color to use for the hightlight action.
  • Delete: Press the Delete button corresponding to an actions you want to remove from the current session.
  • Add: Adds an action to the current session.

2.2.1 Highlight

Enables coloring of the event.

2.2.2 Ignore

Makes the event not to appear in the viewer.

2.2.3 Popup

Pops up a messagebox with the event data.

2.2.4 Highlight match

Enables coloring of the matched content inside the event.

2.2.5 Start ignore

Tells the viewer to start ignoring all events until it receives an End Ignore action.

2.2.6 End ignore

Tells the viewer to start showing events again after ignoring them. The events are not counted so one End will terminate the ignoring even if there has been five Start actions.

2.3 Commandline

You can put any amount (within reason) of filenames on the commandline when starting the application. If there are filenames on the commandline all listeners in the default session will be removed and new ones will be created as described below.
  • A file name with the .l4n extension will remove the default session and start a new according to the settings in the file. The configuration window will not be shown on startup. Make sure this is the first argument on the command line if you intend to add more arguments.
  • A folder name will create a folder listener for that folder.
  • A file name with the .exe extension will start the application with a predefined StdOut listener.
  • Any other file name will create a file listener for that file.

2.3 Default configuration

There is a file in the application folder named DefaultSession.xml which is a file of the same type you get when you save a configuration. By replacing the file you can have another default setup than the one that comes with the install. Remember to save a copy of your file since it will be overwritten by the installer of a new version of the application.

3. Listeners

These are the modules that does most of the actual work. You can add several listeners to one session. Listening at the same resource in more than one session might work for some of the listeners.

3.1 UDP Listener

UDP Listener listens for UDP traffic on a given port.

  • Sender IP: This is the IPv4 adress of the udp package sender.
  • Port: The port to listen on.
  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.

3.2 File Listener

File Listener does a tail on a file.

  • File: Full path to the file to monitor.
  • Poll intervall: How often, in milliseconds, the file should be checked.
  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.
  • Start at end: Whether or not to show all current data in the file or only show new data.

3.3 MS-SQL Listener

MS-SQL Listener does a tail on a table in a Microsoft SQL Server Database

  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.
  • Server: Hostname or IP of the SQL-Server
  • User: Username to use for login.
  • Password: Password to use for login.
  • Windows Authentication: Check this if you want to use windows integrated security to login.
  • Database: The databes to use.
  • Table: The table to watch.
  • Max Column: The column to SELECT MAX from to find new rows.
  • Poll intervall: How often, in milliseconds, to check the table for new rows.
  • Start at end: When this is checked only new items are showed. When it is not checked the listener starts with getting all rows in the table.

3.4 Eventlog Listener

EventLog Listener monitors an event log.

  • Host IP: IP address of the machine hosting the event log.
  • Log name: The eventlog to monitor.
  • Poll intervall: How often, in milliseconds, the eventlog should be checked. This is only used when not monitoring the local machine. The listener uses events for local event logs.
  • Append field names: Whether or not to append the eventlog field names to the log data.
  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.

3.5 RSS and Atom Listener

RSS Listener monitors Atom and RSS feeds.

  • URL: Url to the feed.
  • Poll intervall: How often, in minutes, the feed should be checked.
  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.
  • Start at end: Whether or not to show all current items or start looking for new items.

3.6 Folder Listener

Folder Listener does a tail on all files in a folder.

  • File: Full path to the folder to monitor.
  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.
  • Add filename to prefix: Whether or not to append the filename of the file generating an event to the prefix.
  • Start at end: Whether or not to show all current data in the existing files or only show new data.

3.7 StdOut/StdErr Listener

StdOut/StdErr Listener starts an external application and monitors StdOut and StdError on it.

  • Prefix: A small text that is shown before the event in the viewer to indicate where the event came from.
  • Kill on exit: Whether or not the external application should be terminated when the listener stops.
  • File: Full path including command line arguments to the application.

This is free software.

Please donate to keep the development going.