<?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: Custom Filters in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53582#M10347</link>
    <description>&lt;P&gt;It is not possible to filter using anything other than regular expressions at index time.&lt;/P&gt;

&lt;P&gt;One possible way to achieve this is to replace your file monitor input with a scripted input, and then implement all your filtering logic in the script you write for reading the input data.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Dec 2012 11:00:09 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2012-12-04T11:00:09Z</dc:date>
    <item>
      <title>Custom Filters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53581#M10346</link>
      <description>&lt;P&gt;I'm using the Unversal Forwarder to 'monitor' log files on the clients but I just can't index everything forwarded, there's too much data.&lt;/P&gt;

&lt;P&gt;I know I can use REGEX to filter the data before it's indexed using the nullQueue example in the DOC. That's fine, it's working.&lt;/P&gt;

&lt;P&gt;My problem is that filtering by REGEX is not flexible enough for what I need. Ideally I'd like to plug in a script (python or other) to only let some of the data reach the Indexer.&lt;/P&gt;

&lt;P&gt;Is that possible at all? Or am I chasing a dead-end?&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Didier,&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2012 10:53:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53581#M10346</guid>
      <dc:creator>didier_again</dc:creator>
      <dc:date>2012-12-04T10:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Filters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53582#M10347</link>
      <description>&lt;P&gt;It is not possible to filter using anything other than regular expressions at index time.&lt;/P&gt;

&lt;P&gt;One possible way to achieve this is to replace your file monitor input with a scripted input, and then implement all your filtering logic in the script you write for reading the input data.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2012 11:00:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53582#M10347</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-12-04T11:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Filters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53583#M10348</link>
      <description>&lt;P&gt;That should do. Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2012 11:05:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53583#M10348</guid>
      <dc:creator>didier_again</dc:creator>
      <dc:date>2012-12-04T11:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Filters</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53584#M10349</link>
      <description>&lt;P&gt;(Late comment) Depending on what you're trying to do, you could also use SEDCMD in props.conf to throw away the parts of the events that you don't want indexed.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 15:04:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Custom-Filters/m-p/53584#M10349</guid>
      <dc:creator>DUThibault</dc:creator>
      <dc:date>2018-04-23T15:04:24Z</dc:date>
    </item>
  </channel>
</rss>

