Here you can set how most of the events will look on screen.

Remove surrounding whitespace When checked whitespace around events will be removed befor showing them on screen.

Cache events on pause This will save events in memory and shown when you unpause the viewer.

Show listener header Some listeners add column headers to the events if you check this one.

Save to file If you check this ALL received events will be saved to a file before they are filtered or shown on screen. Rolling decides when the log file is closed and a new one created. This is to stop the file from becoming to big.

Max number of characters in the viewer When there are these many characters in the viewer 10% will be removed from the top. If you don’t need a lot of history you can set this to a low number to save some memory.

flattr this!

,

You can put any amount (within reason) of filenames on the command-line 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.

flattr this!

,

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.

Highlight

Enables coloring of an event.

Ignore

Makes the event not to appear in the viewer.

Popup

Pops up a messagebox with the event data.

Highlight match

Enables coloring of the matched content inside the event.

Start ignore

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

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.

flattr this!

, , , ,

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.

flattr this!

,