<?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: filtering data before indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384558#M94276</link>
    <description>&lt;P&gt;IMO, these configurations should be pushed to both UF and Indexer(s). I've seen filtering not working properly if configs are not present on both source and destination. Worth trying!&lt;/P&gt;</description>
    <pubDate>Fri, 03 Aug 2018 19:35:32 GMT</pubDate>
    <dc:creator>sudosplunk</dc:creator>
    <dc:date>2018-08-03T19:35:32Z</dc:date>
    <item>
      <title>filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384555#M94273</link>
      <description>&lt;P&gt;I'm trying to filter data before it reaches the indexers ON the index server (I'm using universal forwarders...). I've tested on regex101 and verified the regex is good. I'm still seeing data coming in from the 4 IP's.&lt;/P&gt;

&lt;P&gt;I have this setup:&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[Filter_Logs]&lt;BR /&gt;
TRANSFORMS-null = null,Filter_Logs&lt;/P&gt;

&lt;P&gt;transforms.conf&lt;BR /&gt;
[null]&lt;BR /&gt;
REGEX = .&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = indexQueue&lt;/P&gt;

&lt;P&gt;[Filter_Logs]&lt;BR /&gt;
REGEX = (10.1.1.1 -|10.1.1.2 -|10.2.1.1 - |10.2.1.2 -)&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = nullQueue&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 20:43:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384555#M94273</guid>
      <dc:creator>abrice</dc:creator>
      <dc:date>2020-09-29T20:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384556#M94274</link>
      <description>&lt;P&gt;Hi Abrice,&lt;/P&gt;

&lt;P&gt;UF do not have the capability which you are looking for, you need to replace your current universal forwarder with a heavy forwarder. Can copy all of your configuration files from the UF to the HF without having to rewrite anything. &lt;BR /&gt;
Below article helps you configure.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.2/Forwarding/Routeandfilterdatad"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.2/Forwarding/Routeandfilterdatad&lt;/A&gt;&lt;BR /&gt;
Let me know if this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 19:00:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384556#M94274</guid>
      <dc:creator>pruthvikrishnap</dc:creator>
      <dc:date>2018-08-03T19:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384557#M94275</link>
      <description>&lt;P&gt;Thank you for the reply.&lt;/P&gt;

&lt;P&gt;I'm trying to put the filtering on the indexers and not the forwarders as we already have the forwarders deployed and don't want to change that. From what I understand the filtering can be done in either location, either at the forwarders or on the index servers.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 19:06:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384557#M94275</guid>
      <dc:creator>abrice</dc:creator>
      <dc:date>2018-08-03T19:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384558#M94276</link>
      <description>&lt;P&gt;IMO, these configurations should be pushed to both UF and Indexer(s). I've seen filtering not working properly if configs are not present on both source and destination. Worth trying!&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 19:35:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384558#M94276</guid>
      <dc:creator>sudosplunk</dc:creator>
      <dc:date>2018-08-03T19:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384559#M94277</link>
      <description>&lt;P&gt;Just tried that on one web server, no luck.&lt;/P&gt;

&lt;P&gt;on the indexers I've tried it via pushing from the cluster master as an app as well as putting it in etc/system/local &lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 19:54:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384559#M94277</guid>
      <dc:creator>abrice</dc:creator>
      <dc:date>2018-08-03T19:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: filtering data before indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384560#M94278</link>
      <description>&lt;P&gt;Hello, were you able to solve this? If you sense everything is correct, then please revisit your regex again. In your regex (the one in question), I noticed there are &lt;CODE&gt;whitespace&lt;/CODE&gt; characters which seems to be little off. Is it possible to provide some sample events? &lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 15:54:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/filtering-data-before-indexer/m-p/384560#M94278</guid>
      <dc:creator>sudosplunk</dc:creator>
      <dc:date>2018-08-09T15:54:31Z</dc:date>
    </item>
  </channel>
</rss>

