<?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: Filter input data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53294#M10283</link>
    <description>&lt;P&gt;Assuming that you can use a regex to determine which particular events are of interest to you, routing to the nullQueue is the best solution: &lt;A href="http://answers.splunk.com/questions/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk" rel="nofollow"&gt;http://answers.splunk.com/questions/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;If the decision is on a file-by-file basis, whitelists and blacklists in inputs.conf is the best solution.&lt;/P&gt;</description>
    <pubDate>Sat, 18 Sep 2010 06:10:44 GMT</pubDate>
    <dc:creator>Stephen_Sorkin</dc:creator>
    <dc:date>2010-09-18T06:10:44Z</dc:date>
    <item>
      <title>Filter input data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53293#M10282</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;We are looking at deploying splunk for our application servers log files, these log files are about 3GB per day. &lt;/P&gt;

&lt;P&gt;I've had a look around the inputs and it does not seem possible to filter the incoming data.&lt;/P&gt;

&lt;P&gt;Ideally we would be able to place a filer on each input to filter out and collect only Java errors. This is to help cut down on the amount of space we need to store the indexes.&lt;/P&gt;

&lt;P&gt;The only other way i can think to do this is use a scripted input which filters all the data before passing it onto splunk. Basically cat the file and grep out just the errors.&lt;/P&gt;

&lt;P&gt;Can you think of any better way to do this please?&lt;/P&gt;

&lt;P&gt;thank you&lt;/P&gt;</description>
      <pubDate>Sat, 18 Sep 2010 04:40:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53293#M10282</guid>
      <dc:creator>iokoluke</dc:creator>
      <dc:date>2010-09-18T04:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: Filter input data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53294#M10283</link>
      <description>&lt;P&gt;Assuming that you can use a regex to determine which particular events are of interest to you, routing to the nullQueue is the best solution: &lt;A href="http://answers.splunk.com/questions/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk" rel="nofollow"&gt;http://answers.splunk.com/questions/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;If the decision is on a file-by-file basis, whitelists and blacklists in inputs.conf is the best solution.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Sep 2010 06:10:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53294#M10283</guid>
      <dc:creator>Stephen_Sorkin</dc:creator>
      <dc:date>2010-09-18T06:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: Filter input data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53295#M10284</link>
      <description>&lt;P&gt;Thank you for the help!&lt;/P&gt;</description>
      <pubDate>Sat, 18 Sep 2010 06:52:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filter-input-data/m-p/53295#M10284</guid>
      <dc:creator>iokoluke</dc:creator>
      <dc:date>2010-09-18T06:52:45Z</dc:date>
    </item>
  </channel>
</rss>

