<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Sonicwall syslogs and Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157096#M97985</link>
    <description>&lt;P&gt;While I haven't used that myself too much yet, if you know how to distinguish an error event you'd like to index from a non-error event you'd like to discard you can set up regex-based filtering in props.conf/transforms.conf like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;props.conf
[your_sonicwall_sourcetype]
...
TRANSFORMS-filter = setnull,filter_for_errors

transforms.conf
[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[filter_for_errors]
REGEX = some regular expression identifying events you want to keep
DEST_KEY = queue
FORMAT = parsingQueue
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 12 Dec 2014 00:43:51 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-12-12T00:43:51Z</dc:date>
    <item>
      <title>Sonicwall syslogs and Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157095#M97984</link>
      <description>&lt;P&gt;Does anyone out there use Splunk to collect Sonicwall Syslogs? We only have the 2GB splunk license and in hardly touch that. When I turn on the Sonicwall it overloads Splunk with logs. So I'm looking for any recommendations that anyone would have to quiet this thing down. I really only care about errors, I'm not doing any log collecting for compliance or anything like that. I just like to know when things go wrong.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2014 19:34:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157095#M97984</guid>
      <dc:creator>franklucas30</dc:creator>
      <dc:date>2014-12-11T19:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Sonicwall syslogs and Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157096#M97985</link>
      <description>&lt;P&gt;While I haven't used that myself too much yet, if you know how to distinguish an error event you'd like to index from a non-error event you'd like to discard you can set up regex-based filtering in props.conf/transforms.conf like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;props.conf
[your_sonicwall_sourcetype]
...
TRANSFORMS-filter = setnull,filter_for_errors

transforms.conf
[setnull]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[filter_for_errors]
REGEX = some regular expression identifying events you want to keep
DEST_KEY = queue
FORMAT = parsingQueue
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 12 Dec 2014 00:43:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157096#M97985</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-12-12T00:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Sonicwall syslogs and Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157097#M97986</link>
      <description>&lt;P&gt;I was able to figure it out, in there the log settings there is a preconfigured setting for low logging that works perfect.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 20:10:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sonicwall-syslogs-and-Splunk/m-p/157097#M97986</guid>
      <dc:creator>franklucas30</dc:creator>
      <dc:date>2015-01-12T20:10:44Z</dc:date>
    </item>
  </channel>
</rss>

