Stacktrace / Exception column


Author
Message
jkern
jkern
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 8
Hi, I am evaluating LogViewPlus and so far the main issue I have that's preventing me from pulling the trigger is the fact that only the Message column can be set to expand the log entries in the grid vertically. Specifically our logs have stack traces / exceptions in a stack trace column (mapped with the standard JSON Parser as our logs are currently outputting as JSON), but the grid column is effectively useless since exceptions span multiple lines.

As a partial workaround I have mapped the stack trace JSON field to the Message column, in addition to the actual message JSON field being mapped to the Message column.  What this seems to do is map the message to the Message column for any log entries without a stack trace.  Any entries that have a stack trace map it to the Message column, silently hiding the message since only the stack trace appears as the Message.

Is there any way to make LogViewPlus handle stack traces / exceptions better other than writing a custom parser?   Allowing other columns besides Message to expand the grid vertically seems like a fairly standard feature to have.

Thanks
LogViewPlus Support
LogViewPlus Support
I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)
Group: Moderators
Posts: 185, Visits: 720
Hi,

Thanks for bringing this problem to my attention.  The problem makes sense and I agree that LogViewPlus should do a better job of showing Exception columns. 

A simple solution here would be to calculate the height of the message column based on either the message or the exception - taking the larger of the two.  Both columns should benefit from the extra space.  The height will still be constrained by the user setting.  This is a simple change we can put into the next release.

Just to let you know, our BETA release supports automatic syntax highlighting and pretty printing of JSON messages.  Currently, this release has a bug which causes a deadlock which is preventing release, but hopefully we will be able to officially release this feature soon.

Thanks,

Toby




jkern
jkern
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 8
Sounds good, I'll wait to see an upcoming release with the tweak!
LogViewPlus Support
LogViewPlus Support
I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)I'm into this (230 reputation)
Group: Moderators
Posts: 185, Visits: 720
Hi,

I just wanted to let you know that this issue has been resolved in the latest version of LogViewPlus - v2.3.  When calculating grid spacing, LogViewPlus will now use the larger of the message or exception columns (see below).  Note that the exception column will need to be added to the grid manually.



Thanks for bringing this problem to our attention.  Please let me know if you have any further questions or issues.

Toby
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Login

Explore
Messages
Mentions
Search