<?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 Need help filtering at the indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187338#M37445</link>
    <description>&lt;P&gt;We have a service account that populates /var/log/messages on many systems with 3 lines of text every 5 minutes. I'd like to filter that out.&lt;/P&gt;

&lt;P&gt;These entries come in on a single source: /var/log/messages&lt;BR /&gt;
...and a single source type: syslog&lt;/P&gt;

&lt;P&gt;We have 4 indexers that are fed by 12 universal forwarders (in turn fed by many other Windows and linux hosts).&lt;/P&gt;

&lt;P&gt;I'm using a deployment server to successfully deploy props.conf and transforms.conf to each of the indexers.&lt;/P&gt;

&lt;P&gt;This is my entry in props.conf;&lt;/P&gt;

&lt;P&gt;[syslog]&lt;BR /&gt;
TRANSFORMS-set = setnull&lt;/P&gt;

&lt;P&gt;This is my entry in transfro&lt;/P&gt;

&lt;P&gt;[setnull]&lt;BR /&gt;
REGEX = svc_scomlinux&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = nullQueue&lt;/P&gt;

&lt;P&gt;I expect any entries coming in on the source/sourcetype and containing the text svc_scomlinux to be discarded, but it's still coming through.&lt;/P&gt;

&lt;P&gt;I spent a good part of the day reading answers here, docs and other sources on the web but I'm not getting any traction. What am I missing?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 19:53:44 GMT</pubDate>
    <dc:creator>pipegrep</dc:creator>
    <dc:date>2020-09-28T19:53:44Z</dc:date>
    <item>
      <title>Need help filtering at the indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187338#M37445</link>
      <description>&lt;P&gt;We have a service account that populates /var/log/messages on many systems with 3 lines of text every 5 minutes. I'd like to filter that out.&lt;/P&gt;

&lt;P&gt;These entries come in on a single source: /var/log/messages&lt;BR /&gt;
...and a single source type: syslog&lt;/P&gt;

&lt;P&gt;We have 4 indexers that are fed by 12 universal forwarders (in turn fed by many other Windows and linux hosts).&lt;/P&gt;

&lt;P&gt;I'm using a deployment server to successfully deploy props.conf and transforms.conf to each of the indexers.&lt;/P&gt;

&lt;P&gt;This is my entry in props.conf;&lt;/P&gt;

&lt;P&gt;[syslog]&lt;BR /&gt;
TRANSFORMS-set = setnull&lt;/P&gt;

&lt;P&gt;This is my entry in transfro&lt;/P&gt;

&lt;P&gt;[setnull]&lt;BR /&gt;
REGEX = svc_scomlinux&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = nullQueue&lt;/P&gt;

&lt;P&gt;I expect any entries coming in on the source/sourcetype and containing the text svc_scomlinux to be discarded, but it's still coming through.&lt;/P&gt;

&lt;P&gt;I spent a good part of the day reading answers here, docs and other sources on the web but I'm not getting any traction. What am I missing?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:53:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187338#M37445</guid>
      <dc:creator>pipegrep</dc:creator>
      <dc:date>2020-09-28T19:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: Need help filtering at the indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187339#M37446</link>
      <description>&lt;P&gt;This looks correct to me, unless you have misspelled &lt;CODE&gt;transforms.conf&lt;/CODE&gt; or something silly like that.  Are you getting any errors when you start Splunk saying that it cannot find &lt;CODE&gt;setnull&lt;/CODE&gt;?  You should use btool to check out what configurations are actually in place.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2015 15:30:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187339#M37446</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-19T15:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Need help filtering at the indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187340#M37447</link>
      <description>&lt;P&gt;It indeed was something silly. Ultimately I found that my search heads were actually running heavy forwarders and were outside of my deployment changes, subsequently spewing out the events. Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2015 13:45:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Need-help-filtering-at-the-indexer/m-p/187340#M37447</guid>
      <dc:creator>pipegrep</dc:creator>
      <dc:date>2015-05-21T13:45:09Z</dc:date>
    </item>
  </channel>
</rss>

