Stacktrace / Exception column


Author
Message
jkern
jkern
New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 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
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Login

Explore
Messages
Mentions
Search