﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>LogViewPlus Support » LogViewPlus Support » Features &amp; Suggestions  » Row Filters based on patern</title><generator>InstantForum 2017-1 Final</generator><description>LogViewPlus Support</description><link>https://www.logviewplus.com/forum/</link><webMaster>LogViewPlus Support</webMaster><lastBuildDate>Wed, 06 May 2026 23:21:59 GMT</lastBuildDate><ttl>20</ttl><item><title>Row Filters based on patern</title><link>https://www.logviewplus.com/forum/post/86</link><description>Hi Team (again)!&lt;br/&gt;&lt;br/&gt;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!&lt;br/&gt;&lt;br/&gt;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!&lt;br/&gt;&lt;br/&gt;Cheers,&lt;br/&gt;Michael.</description><pubDate>Tue, 12 Feb 2019 07:46:23 GMT</pubDate><dc:creator>falconmick</dc:creator></item><item><title>RE: Row Filters based on patern</title><link>https://www.logviewplus.com/forum/post/88</link><description>Hi Michael,&lt;br/&gt;&lt;br/&gt;What I would expect to happen is the unparsed line shows up as part of the message of the previous log entry.&amp;nbsp; In the case of the header, it should be in the message of the first log entry.&amp;nbsp; I am not sure why it is changing the priority to Fatal.&amp;nbsp; This may be a bug.&amp;nbsp; I may be able to help more if I could see your pattern and a few sample log entries.&lt;br/&gt;&lt;br/&gt;It might help in this case if you create a multi-pattern parse.&amp;nbsp; You could then parse the headers and footers which should make it easier to filter them out.&amp;nbsp; &amp;nbsp;Multi-patterns are described at the bottom of this page:&lt;br/&gt;&lt;a href="https://www.logviewplus.com/docs/pattern_parser.html"&gt;https://www.logviewplus.com/docs/pattern_parser.html&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;You could also write a custom plugin, but this would require distribution on all machines where you use LogViewPlus:&lt;br/&gt;&lt;a href="https://www.logviewplus.com/docs/post_processors.html"&gt;https://www.logviewplus.com/docs/post_processors.html&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Unfortunately, I don't think this is something we can put into LogViewPlus as a feature.&amp;nbsp; The issue is that it would increase configuration complexity to solve a uncommon problem.&amp;nbsp; Complexity is a struggle with an application like LogViewPlus and something we work hard to keep at a minimum.&lt;br/&gt;&lt;br/&gt;Thanks,&lt;br/&gt;&lt;br/&gt;Toby&lt;br/&gt;&lt;br/&gt;</description><pubDate>Tue, 12 Feb 2019 07:46:23 GMT</pubDate><dc:creator>LogViewPlus Support</dc:creator></item></channel></rss>