Feature Suggestion: Parse into arbitrary fields

If you think LogMX needs a new useful feature!
Post Reply
wcgraham
Posts: 3
Joined: Fri Nov 23, 2007 11:36 pm

Feature Suggestion: Parse into arbitrary fields

Post by wcgraham » Sat Nov 24, 2007 12:28 am

I call this a 'feature suggestion' because I don't know if this is really my requirement or anyone else's, but I have a nagging feeling that the need would come up.

Your app seems built around 6 specific fields for a log entry, and any other items, even ones common to Log4j, can only get appended into the catch-all message text, or else ignored.

It is useful that the app has a semantic understanding of certain key fields -- emitters can be filtered in a hierarchy, levels can be filtered in a continuum, timestamps can be compared and calculated with.

But it would also be useful for a Parser to be able to extract part of the log entry to a user-defined field name, and then allow these fields to participate the same kinds of operations that the Message field can. Such as, making an alert/search term that says eg.: [ConnectionPool] = 'ReadOnly', or [TransactionLevel] > 1, or [DbProc] contains 'User' ... or whatever.

Mind you, the above examples imply fields that may be present or absent in any given log entry; thus, they would probably have to be specified as expressions that include marker text, which is not considered part of the found value, and the value itself.

That would be a bigger job than the simpler task of skinning log columns that are always present [or their placeholders/demarcations are always present] in a designated order -- which would be useful enough for many cases.

The first reason this tweaked me, is I know that Chainsaw, which as far as I can tell is much less useful than your application, provides a field/column for NestedDebugContext. Now, I've never used that field, but if I was using it, I'd hate to have to choose between using the field [in a nice way, where it is its own column] and using your app with the nice features that it has.

Just wishful thinking on a Friday, but I hope the idea is not a complete waste of bandwidth to mention.

Cheers,

Chris

admin
Site Admin
Posts: 421
Joined: Sun Dec 17, 2006 10:30 pm

Post by admin » Sun Nov 25, 2007 11:59 pm

This is a good idea: each log entry could have a 'hash table' filled by the parser, for example:
[ConnectionPool] = 'ReadOnly',
[TransactionLevel] = 1
[DbProc] = <null> (if no information found in file for this field)

Then LogMX would also display these extra fields only if they are set for at least one entry.

In the meantime, you can use these extra field to participate the same kinds of operations that the Message field can: using the log4j pattern syntax and its 'catch-all' function in message field, you can search entries or define alerts using these fields since 'message' field starts with [<field_name>=<field_value>]. But I agree, matches will be less impressive since 'Message' field contains other data.

Xavier.

isheedm
Posts: 109
Joined: Wed Sep 12, 2007 2:16 pm

Post by isheedm » Mon Nov 26, 2007 4:15 pm

I also like the idea of having arbitrary fields that are parsed out of a log message. I would then like to have the option to show that field in the table panel, or just show them in the Message. I would also want to be able to search / filter on them.

admin
Site Admin
Posts: 421
Joined: Sun Dec 17, 2006 10:30 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by admin » Sat Mar 20, 2010 3:20 pm

Hello,

LogMX v2.0.0 is now available, and includes this new feature. Such log entry fields have been called "user-defined fields", are displayed in a dedicated column, and can be used in Search & Filter features.

Feel free to let me know if you have questions or problems using this new feature.

Xavier.

isheedm
Posts: 109
Joined: Wed Sep 12, 2007 2:16 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by isheedm » Thu May 27, 2010 2:34 pm

I would like the ability to turn off the new columns by right clicking the table header like I can with the default ones.

For example, I added "Line" and "File" to the Message, but at the moment, I don't want to see them in the table.

admin
Site Admin
Posts: 421
Joined: Sun Dec 17, 2006 10:30 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by admin » Thu May 27, 2010 5:38 pm

Hello,

OK for this feature request.
In the meantime, if you use a Log4j Pattern Parser, you can turn off these new columns "Line" and "File" in the Parser creation dialog, using the Log4j tags settings editor (button "Tag settings >>" at the right of the Parser creation dialog). Just check "Ignore" for tags you don't want to see in the main table.

Xavier.

isheedm
Posts: 109
Joined: Wed Sep 12, 2007 2:16 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by isheedm » Thu May 27, 2010 6:34 pm

I do want to see them in the message though.

admin
Site Admin
Posts: 421
Joined: Sun Dec 17, 2006 10:30 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by admin » Thu May 27, 2010 8:52 pm

OK :?
I will let you know when this feature is available

admin
Site Admin
Posts: 421
Joined: Sun Dec 17, 2006 10:30 pm

Re: Feature Suggestion: Parse into arbitrary fields

Post by admin » Tue Aug 31, 2010 5:01 pm

Hello,

LogMX v2.0.2 is now available: you can now hide user-defined columns.

Xavier

Post Reply