<?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: How can we identify forwarders which are not connected to certain indexers? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248767#M47868</link>
    <description>&lt;P&gt;I know this isn't what you're asking, but having hundreds of forwarders going directly to your indexers is against best practice. The Heavy Forwarder role should be intercepting these messages from the UFs and such and then forwarding them to the indexers.&lt;/P&gt;

&lt;P&gt;This also allows you to do some preprocessing with transforms and props that would otherwise take resources away from your indexers.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Aug 2016 19:28:01 GMT</pubDate>
    <dc:creator>rharrisssi</dc:creator>
    <dc:date>2016-08-26T19:28:01Z</dc:date>
    <item>
      <title>How can we identify forwarders which are not connected to certain indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248766#M47867</link>
      <description>&lt;P&gt;The DMC shows us the following - &lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1770i5BAC257FE2D1B082/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;It shows the connected forwarders to the four indexers, the yellow line is actually two indexers one on top of the other.&lt;/P&gt;

&lt;P&gt;How can we figure out which two hundred or so forwarders are not connected to the two newer indexers (the blue and purple) at the bottom of the chart?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 19:24:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248766#M47867</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-08-26T19:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: How can we identify forwarders which are not connected to certain indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248767#M47868</link>
      <description>&lt;P&gt;I know this isn't what you're asking, but having hundreds of forwarders going directly to your indexers is against best practice. The Heavy Forwarder role should be intercepting these messages from the UFs and such and then forwarding them to the indexers.&lt;/P&gt;

&lt;P&gt;This also allows you to do some preprocessing with transforms and props that would otherwise take resources away from your indexers.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 19:28:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248767#M47868</guid>
      <dc:creator>rharrisssi</dc:creator>
      <dc:date>2016-08-26T19:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: How can we identify forwarders which are not connected to certain indexers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248768#M47869</link>
      <description>&lt;P&gt;Jeff suggested - &lt;/P&gt;

&lt;P&gt;-- You should be able to run a search on &lt;CODE&gt;_internal&lt;/CODE&gt; for the last 24 hours looking for host whose count of &lt;CODE&gt;splunk_server != 4&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Aug 2016 00:12:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-we-identify-forwarders-which-are-not-connected-to/m-p/248768#M47869</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2016-08-29T00:12:00Z</dc:date>
    </item>
  </channel>
</rss>

