﻿<?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 » Configuration &amp; Customization  » Sonicwall parser</title><generator>InstantForum 2017-1 Final</generator><description>LogViewPlus Support</description><link>https://www.logviewplus.com/forum/</link><webMaster>LogViewPlus Support</webMaster><lastBuildDate>Mon, 11 May 2026 07:35:35 GMT</lastBuildDate><ttl>20</ttl><item><title>Sonicwall parser</title><link>https://www.logviewplus.com/forum/post/491</link><description>I'm trying to set up a parser for the Sonicwall firewall.&lt;br/&gt;I stop at moment on message.&lt;br/&gt;I have two similar messages:&lt;br/&gt;msg="Connection Closed" app=7927 n=12234655 &lt;br/&gt;msg="Connection Opened" app=49177 appName="General HTTPS" n=5319205&lt;br/&gt;as you see on one is "appName". I worry that If this is missing in line, the parser will give me en error. Or not?&lt;br/&gt;At moment whole message is in one column but I want to split it into different columns.</description><pubDate>Wed, 08 Apr 2020 09:57:00 GMT</pubDate><dc:creator>marcin.wrazidlo</dc:creator></item><item><title>RE: Sonicwall parser</title><link>https://www.logviewplus.com/forum/post/493</link><description>Hi Toby&lt;br/&gt;Thanks for your response and info.&lt;br/&gt;I will look into this multi parser.&lt;br/&gt;&lt;br/&gt;Regarding key-value I think this will be useful in some cases, so waiting to hear about a new version of your app.&amp;nbsp;&lt;br/&gt;&lt;br/&gt;Marcin</description><pubDate>Wed, 08 Apr 2020 09:57:00 GMT</pubDate><dc:creator>marcin.wrazidlo</dc:creator></item><item><title>RE: Sonicwall parser</title><link>https://www.logviewplus.com/forum/post/492</link><description>Hi Marcin,&lt;br/&gt;&lt;br/&gt;You are correct - the LogViewPlus PatternParser cannot parse 'optional' fields.&amp;nbsp; Often, the best thing to do in these situations is to parse the message into one column.&lt;br/&gt;&lt;br/&gt;However, if you only have a small number of optional fields, it may be worth considering a &lt;a href="https://www.logviewplus.com/docs/multi_patterns.html" id="if_insertedNode_1586338071800"&gt;Multi-Pattern&lt;/a&gt;.&amp;nbsp; Multi-patterns allow for multiple parsing patterns to be configured.&amp;nbsp; If the first one fails, the second one is used.&amp;nbsp; This might work in your scenario, but it starts to break down if fields can be provided out of order or if there are a lot of fields.&lt;br/&gt;&lt;br/&gt;You might also want to consider writing a &lt;a href="https://www.logviewplus.com/docs/custom_parsers.html" id="if_insertedNode_1586338216194"&gt;customer parser&lt;/a&gt;.&lt;br/&gt;&lt;br/&gt;I think what is really needed here is some kind of key-value-pair parser.&amp;nbsp; I can see where this would be helpful and will take a look for the next release.&amp;nbsp; I will post back here when I have something available.&lt;br/&gt;&lt;br/&gt;Hope that helps,&lt;br/&gt;&lt;br/&gt;Toby&lt;br/&gt;</description><pubDate>Wed, 08 Apr 2020 09:33:07 GMT</pubDate><dc:creator>LogViewPlus Support</dc:creator></item></channel></rss>