<?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 How to blacklist data containing specific words in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-data-containing-specific-words/m-p/424708#M74483</link>
    <description>&lt;P&gt;I have found that there are lots of syslog contains &lt;STRONG&gt;"Log statistics"&lt;/STRONG&gt;, which is log statistic data of syslog. &lt;BR /&gt;
Splunk could not parse it well and I do not want to index this data. &lt;/P&gt;

&lt;P&gt;How I can blacklist it in the inputs.conf?&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2019 23:10:29 GMT</pubDate>
    <dc:creator>bli_scs</dc:creator>
    <dc:date>2019-06-12T23:10:29Z</dc:date>
    <item>
      <title>How to blacklist data containing specific words</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-data-containing-specific-words/m-p/424708#M74483</link>
      <description>&lt;P&gt;I have found that there are lots of syslog contains &lt;STRONG&gt;"Log statistics"&lt;/STRONG&gt;, which is log statistic data of syslog. &lt;BR /&gt;
Splunk could not parse it well and I do not want to index this data. &lt;/P&gt;

&lt;P&gt;How I can blacklist it in the inputs.conf?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 23:10:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-data-containing-specific-words/m-p/424708#M74483</guid>
      <dc:creator>bli_scs</dc:creator>
      <dc:date>2019-06-12T23:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist data containing specific words</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-data-containing-specific-words/m-p/424709#M74484</link>
      <description>&lt;P&gt;@bli_scs&lt;/P&gt;

&lt;P&gt;From the inputs.conf we can do the blacklisting at file or directory level. See here - &lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/latest/Data/Whitelistorblacklistspecificincomingdata#Blacklist_.28ignore.29_files"&gt;https://docs.splunk.com/Documentation/SplunkCloud/latest/Data/Whitelistorblacklistspecificincomingdata#Blacklist_.28ignore.29_files&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;However to perform the blacklisting which is event based (on some criteria like in your case that the event contains "Log statistics"), you can use a Heavy Forwarder, which processes both the input phase and the parsing phase before forwarding. &lt;BR /&gt;
and on your HF, you can define the filtering rule on your props.conf and transforms.conf&lt;BR /&gt;
For defining a filtering rule, this post can help you - &lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/59370/filtering-events-using-nullqueue-1.html"&gt;https://answers.splunk.com/answers/59370/filtering-events-using-nullqueue-1.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Please accept as answer if this responds to your query.&lt;BR /&gt;
Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 13:39:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-data-containing-specific-words/m-p/424709#M74484</guid>
      <dc:creator>amitm05</dc:creator>
      <dc:date>2019-06-13T13:39:13Z</dc:date>
    </item>
  </channel>
</rss>

