Advanced Specifiers

All log files can be parsed using the 7 convsersion specifiers described in Specifier Basics. However, LogViewPlus supports over thirty different conversion specifiers. That is because we wanted to give you the maximum amount of control over how your log file is parsed.

There are two advantages of using the advanced conversion specifiers:

1. Anything parsed and understood by LogViewPlus will have its own dedicated column in the Log Entry Grid.

2. If you are creating your own custom filters, you will have all parsed fields available to you in a field with a dedicated name. This will make your code easier to read and support. Unparsed or generic fields (like %s) are still available, but may be harder to access and interpret.

The full list of conversion specifiers and their corresponding grid column names are shown below. Note that some specifiers have aliases.

Specifier
Grid Column
Notes
%a
%appdomain
AppDomain
%aspnet-cache
Web Cache
%aspnet-context
Web Context
%aspnet-request
Web Request
%aspnet-session
Web Session
%C
%class
%type
Class
%d
%date
Date + Time
This field is split across two grid columns. This makes it easy to remove the date column if it is not adding value.
%ex
%exception
%throwable
%rex
%rexception
%rthrowable
%xex
%xexception
%xthrowable
%stacktrace
%stacktracedetail
Exception
%F
%file
File Name
%highlight
N/A
This field does not affect the way a log entry is parsed. It has been included for compatibility with Apache Log4 conversion patterns.
%l
%location
Location
%L
%line
Line Number
%c
%logger
Logger
%m
%msg
%message
Message
%M
%method
MethodName
%x
%ndc
NDC
%n
%newline
N/A
Marker for the end of a log entry.
%%
N/A
%p
%level
Priority
%t
%thread
Thread
%r
%timestamp
%relative
See 'Date'.
%w
%username
Username
%utcdate
See 'Date'.
%marker
N/A
%replace
N/A
This field does not affect the way a log entry is read. It has been included for compatibility with Apache Log4 conversion patterns.
%sn
%sequencenumber
Sequence Number
%style
N/A
This field does not affect the way a log entry is read. It has been included for compatibility with Apache Log4 conversion patterns.
%u
%identity
Identity
%uuid
UUID
%s
N/A
For parsing a single word. Items added as strings will not be available in the LogViewPlus grid by default. To add them to the grid, specify a column name with an argument like %s{Column_Name}. If you were to build a custom filter, you would find string data available under the LogEntry.Strings property.
%S
N/A
For parsing multiple words. See above.
%P
%K
%X
%key
%map
%mdc
%property
%properties
N/A
These properties will not be available in the LogViewPlus grid, but will be available in the LogEntry. If you were to build a custom filter, you would find property data available under the LogEntry.Properties property.
Log File
The log file where the log entry was parsed. Useful when working with merged views.
This grid column is available on all log files. To view it, simply select the column from the 'Add Columns' command.
Log Line Number
The line number in the log file where this entry was found. Useful if you need to refer to the underlying text file.
This grid column is available on all log files. To view it, simply select the column from the 'Add Columns' command.

Important: Because LogViewPlus does not write a log file, it has no way to confirm that the field displayed actully matches the relevant data. For example, the %appdomain specifier simply specifies a string which will be available through the AppDomain column in the grid. LogViewPlus has no way of knowing whether this field is actually a .Net Application domain. This relationship is assumed.

< >