Hi Team (again)!

I would love the ability in my parser to add a filter that nulls out an entire row if it matches my filter/regex thing! Basically every time my app stops and starts my logger automatically places a header and footer to the log file so I can better track when the app has stoped and stared. Unfortunately this log doesn't follow my files parser and causes Fatal logs to be mistakenly made!

My short term solution was to remove the header and footer from my logger and I plan now to just make a new header and footer which follows the pattern so its parsed as an info, however I would love it if I could just filter a row out!

Cheers,
Michael.

Hi Michael,

What I would expect to happen is the unparsed line shows up as part of the message of the previous log entry.  In the case of the header, it should be in the message of the first log entry.  I am not sure why it is changing the priority to Fatal.  This may be a bug.  I may be able to help more if I could see your pattern and a few sample log entries.

It might help in this case if you create a multi-pattern parse.  You could then parse the headers and footers which should make it easier to filter them out.   Multi-patterns are described at the bottom of this page:
https://www.logviewplus.com/docs/pattern_parser.html

You could also write a custom plugin, but this would require distribution on all machines where you use LogViewPlus:
https://www.logviewplus.com/docs/post_processors.html

Unfortunately, I don't think this is something we can put into LogViewPlus as a feature.  The issue is that it would increase configuration complexity to solve a uncommon problem.  Complexity is a struggle with an application like LogViewPlus and something we work hard to keep at a minimum.

Thanks,

Toby