Unable to parse logs after updating to 2.5.22


Author
Message
petr
petr
Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)Junior Member (82 reputation)
Group: Forum Members
Posts: 7, Visits: 19
After updating to 2.5.22 the json log files that worked fine in older version now fail to parse.
I couldn't find a link to older versions. Can you please provide archive of older versions, or at least the last one before 2.5.22 (I don't know which one it was).

I can provide the failing log and parser if you want.
Replies
Tim
Tim
New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)New Member (13 reputation)
Group: Forum Members
Posts: 1, Visits: 4
[quote]
LogViewPlus Support - 28 Jul 2021
Second, I noticed that our CLEF message template processing was not automatically detecting the 'Properties' object favored by Serilog.  We have addressed this issue as well.  If you want to clean-up your parser configuration a bit, you should be able to get a good parse with:

{
  "Timestamp": "%d{yyyy-MM-ddT%H:mm:ss.fffffffzzzz}",
  "Level": "%p",
  "MessageTemplate": "%m{-parserhint:CLEF}",
  "Exception": "%ex"
}


Hi Toby,

Is it possible to configure logviewplus to find the variables in an object called something other than 'Properties'? Apologies if I missed it in the docs

Thanks
Tim

LogViewPlus Support
LogViewPlus Support
Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)
Group: Moderators
Posts: 1.3K, Visits: 4.5K
Hi Tim,

Right now, LogViewPlus can find the variables in the root node, or in the 'Properties' object.  This search path is not configurable. 

What object are you trying to read from?  Is your logging format part of a standard?

Maybe what we need to do is expand the parser hint to something like "%m{-parserhint:CLEF  MY_PROPERTIES_OBJECT}"

Toby
Edited 5 Years Ago by LogViewPlus Support
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View
Threaded View
petr - 5 Years Ago
LogViewPlus Support - 5 Years Ago
petr - 5 Years Ago
LogViewPlus Support - 5 Years Ago
petr - 5 Years Ago
                         Hi Petr, Thanks for sending the sample log file across. I have now...
LogViewPlus Support - 5 Years Ago
                             Hi Petr, Apologies for the delay in getting back to you. We normally...
LogViewPlus Support - 5 Years Ago
                                 Hi Toby, wow, that all sounds great! Thanks, I'll definitely try out...
petr - 5 Years Ago
                                 Hi Toby, Is it possible to configure logviewplus to find the...
Tim - 5 Years Ago
                                     Hi Tim, Right now, LogViewPlus can find the variables in the root...
LogViewPlus Support - 5 Years Ago

Similar Topics

Login

Explore
Messages
Mentions
Search