<?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: Find rogue splunk servers in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117605#M31339</link>
    <description>&lt;P&gt;Hi omgwut56k,&lt;/P&gt;

&lt;P&gt;if I get you correct, you wants to stop or reconfigure some search heads and have them stop forwarding their &lt;CODE&gt;_internal&lt;/CODE&gt; index - right?&lt;BR /&gt;&lt;BR /&gt;
There are a few things you should keep in mind tough:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;it is not a good practice not to forward the &lt;CODE&gt;_internal&lt;/CODE&gt;, since it makes troubleshooting much more complicated.&lt;/LI&gt;
&lt;LI&gt;What is your intension to do so? If it's about the data amount send, then rather fix any problem on that search head than stop forwarding.&lt;/LI&gt;
&lt;LI&gt;If your concern is about license; &lt;CODE&gt;_internal&lt;/CODE&gt; does not count on the license and has a default retention of 30 days.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;But back to your question; this is pretty easy, login to any search head that has all your indexers are search peer and run:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal | stats count by host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will get a table of all splunk server sending their &lt;CODE&gt;_internal&lt;/CODE&gt; events to the indexer.&lt;/P&gt;

&lt;P&gt;Hope that helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Sun, 24 May 2015 23:46:50 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-05-24T23:46:50Z</dc:date>
    <item>
      <title>Find rogue splunk servers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117602#M31336</link>
      <description>&lt;P&gt;I have a list of computers running splunkweb , I am trying to remove results that are logging to the _internal index which would indicate the servers are part of our main infrastructure.&lt;/P&gt;

&lt;P&gt;How can I filter out hosts that have reported to events to the _internal index?&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2015 16:31:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117602#M31336</guid>
      <dc:creator>omgwut56k</dc:creator>
      <dc:date>2015-05-22T16:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: Find rogue splunk servers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117603#M31337</link>
      <description>&lt;P&gt;I do not understand; all Splunk servers should log to _index.  That is kind of the entire point.&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2015 02:44:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117603#M31337</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-23T02:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: Find rogue splunk servers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117604#M31338</link>
      <description>&lt;P&gt;Do you perhaps mean &lt;CODE&gt;main&lt;/CODE&gt; instead of &lt;CODE&gt;_index&lt;/CODE&gt;?&lt;/P&gt;</description>
      <pubDate>Sun, 24 May 2015 03:57:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117604#M31338</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-24T03:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: Find rogue splunk servers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117605#M31339</link>
      <description>&lt;P&gt;Hi omgwut56k,&lt;/P&gt;

&lt;P&gt;if I get you correct, you wants to stop or reconfigure some search heads and have them stop forwarding their &lt;CODE&gt;_internal&lt;/CODE&gt; index - right?&lt;BR /&gt;&lt;BR /&gt;
There are a few things you should keep in mind tough:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;it is not a good practice not to forward the &lt;CODE&gt;_internal&lt;/CODE&gt;, since it makes troubleshooting much more complicated.&lt;/LI&gt;
&lt;LI&gt;What is your intension to do so? If it's about the data amount send, then rather fix any problem on that search head than stop forwarding.&lt;/LI&gt;
&lt;LI&gt;If your concern is about license; &lt;CODE&gt;_internal&lt;/CODE&gt; does not count on the license and has a default retention of 30 days.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;But back to your question; this is pretty easy, login to any search head that has all your indexers are search peer and run:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal | stats count by host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will get a table of all splunk server sending their &lt;CODE&gt;_internal&lt;/CODE&gt; events to the indexer.&lt;/P&gt;

&lt;P&gt;Hope that helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Sun, 24 May 2015 23:46:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-rogue-splunk-servers/m-p/117605#M31339</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-05-24T23:46:50Z</dc:date>
    </item>
  </channel>
</rss>

