#8 Standard and custom Message Formats
Define a "standard" logformat (conversion pattern in
log4net). A simple possible example is:
<param name="ConversionPattern" value="@@MyAppName@@%d{HH:mm:ss}@@%5p@@%m"/>
The user would need to choose the Standard Message
Format, Unformatted, or maybe create their own format.
One of the benefits is that we can get both more and
better information. For instance, by parsing the
incoming message
created by a format similar to the example above we
know the application name, the time of the message from
the client (not the time we received it), the class
name, etc.
Benefits:
We could display extra columns if the standard format
is used. For example, AppName. AppName would be very
beneifical where several apps all log from the same client.
Filtering. There is a feature request for filtering
which could include the extra columns.
Also, allowing the user to define there own format
could allow filtering on custom values.
Coloring could be done on a specific column called
"Priority"
