<?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 a Universal Forwarder? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281472#M53828</link>
    <description>&lt;P&gt;This should be relatively simple, but I cannot find discussion or documentation on it. I suspect that Splunk assumes if a universal forwarder is installed, the data is wanted. The problem is that there is a UF out of my control with a misconfigured index name. I would like to blacklist it until the owner can fix it.&lt;/P&gt;

&lt;P&gt;How would I blacklist a UF?&lt;/P&gt;</description>
    <pubDate>Mon, 06 Jun 2016 14:01:16 GMT</pubDate>
    <dc:creator>ccsfdave</dc:creator>
    <dc:date>2016-06-06T14:01:16Z</dc:date>
    <item>
      <title>How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281472#M53828</link>
      <description>&lt;P&gt;This should be relatively simple, but I cannot find discussion or documentation on it. I suspect that Splunk assumes if a universal forwarder is installed, the data is wanted. The problem is that there is a UF out of my control with a misconfigured index name. I would like to blacklist it until the owner can fix it.&lt;/P&gt;

&lt;P&gt;How would I blacklist a UF?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 14:01:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281472#M53828</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2016-06-06T14:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281473#M53829</link>
      <description>&lt;P&gt;Do you control the UF from your deployment server?  If not you should.&lt;/P&gt;

&lt;P&gt;Your options are blocking the src_ip at the firewall... (iptables on linux, windows firewall will do the trick too)&lt;/P&gt;

&lt;P&gt;Asking UF owner to turn off UF.&lt;/P&gt;

&lt;P&gt;IF you have UF password you can probably disable via REST calls.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 14:48:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281473#M53829</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-06-06T14:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281474#M53830</link>
      <description>&lt;P&gt;Well, I let the question stand because I figured some good discussion or tips may come from it but it was in my DS so I  took care of it (i think) from there.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 14:52:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281474#M53830</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2016-06-06T14:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281475#M53831</link>
      <description>&lt;P&gt;I assume splunk doesn't want you to blacklist forwarders because they should be controlled via the DS.  And if you had a config file somewhere blacklisting them you might spend days trying to figure out why they arent sending data in, etc.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 15:17:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281475#M53831</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-06-06T15:17:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281476#M53832</link>
      <description>&lt;P&gt;Yeah, that makes sense&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 15:41:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281476#M53832</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2016-06-06T15:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281477#M53833</link>
      <description>&lt;P&gt;Like this:&lt;/P&gt;

&lt;P&gt;1: In props.conf, set the TRANSFORMS-null attribute:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::BadUniversalForwarderHostIdentifierHere]
TRANSFORMS-null = TrashEverything
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;2: Create a corresponding stanza in transforms.conf. Set &lt;CODE&gt;DEST_KEY&lt;/CODE&gt; to &lt;CODE&gt;queue&lt;/CODE&gt; and &lt;CODE&gt;FORMAT&lt;/CODE&gt;to &lt;CODE&gt;nullQueue&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[TrashEverything]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;3: Deploy to all Indexers and restart all Splunk instances there.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 15:44:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281477#M53833</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-06-06T15:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281478#M53834</link>
      <description>&lt;P&gt;Yeah this is great option if you can restart indexers.  The "blacklisting" word put me in a different direction, but nullQueueing is in effect the same.  Thanks woodcock!&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 15:47:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281478#M53834</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-06-06T15:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: How to blacklist a Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281479#M53835</link>
      <description>&lt;P&gt;Yeah, I have full control of the central Splunk Infrastructure: SH, Indexers, HF, DS.  So, Let me accept this and will update the answer if I need to in the future.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 16:00:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-blacklist-a-Universal-Forwarder/m-p/281479#M53835</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2016-06-06T16:00:34Z</dc:date>
    </item>
  </channel>
</rss>

