By May - 23 Jan 2024
It would be great if LogViewPlus would not cancel parsing when it encounters a corrupt log entry but just try to skip the broken entry and continue with the next. This is the way "Log4View" works.
-Matej
|
By LogViewPlus Support - 23 Jan 2024
Hi May,
Usually what LogViewPlus does in this case is append the corrupt log entry on to the previous log entry. If you can tell me more about the cancellation, I may be able to help. Would it be possible to post a sample log entry?
Thanks,
Toby
|
By May - 24 Jan 2024
Our logger seems to have a threading problem so it happens the one log item (log4net) is interrupted by another one. So I have to remove these corrupt item manually from the logfile and retry parsing. Log4View can handle this by simply skipping the broken item. It would be great if LogViewPlus would also be able to do so.
|
By LogViewPlus Support - 28 Jan 2024
Skipping log items isn't a very good solution as it might lead to important data being hidden.
It is not clear why the corrupt items are causing issues as LogViewPlus should just append the invalid log entry to the previous entry. Are you able send me a sample log entry and more information on how the log file is being parsed?
|
By May - 30 Jan 2024
The solution for me is to use the "Pattern Parser" instead of the "XML Parser". Thanks for your help
|
By LogViewPlus Support - 31 Jan 2024
Glad to hear the solution we discussed offline helped - thanks for letting me know!
For anyone else finding this post, when a strict parser such as XML or JSON is being used and the underlying log entry is invalid, the entire file will fail to parse. This is by design to ensure no data is lost when searching the file.
As highlighted above, the work-around for this behaviour is to use a more generic parser type.
|