<?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 where a forwarder is forwarding too in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90108#M23104</link>
    <description>&lt;P&gt;That does seem to bring a few up with the expected results but by no means all, do you have any further advice ?&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2013 08:47:29 GMT</pubDate>
    <dc:creator>AaronMoorcroft</dc:creator>
    <dc:date>2013-10-10T08:47:29Z</dc:date>
    <item>
      <title>Find where a forwarder is forwarding too</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90105#M23101</link>
      <description>&lt;P&gt;Hey Guys&lt;/P&gt;

&lt;P&gt;I have multiple DMZs with forwarders all over the places that send to specific main forwarders if you like and then onto the indexer, is there a search that anyone knows of that I can run on a host to tell me where that device is set to forward too, I have a few boxs I need to jump on but its would be better if I can run a search as to jumping through hoops to log onto the actual device its self.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Aaron&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 10:47:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90105#M23101</guid>
      <dc:creator>AaronMoorcroft</dc:creator>
      <dc:date>2013-10-09T10:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: Find where a forwarder is forwarding too</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90106#M23102</link>
      <description>&lt;P&gt;Hi AaronMoorcroft&lt;/P&gt;

&lt;P&gt;assuming your forwarders are forwarding their &lt;CODE&gt;_internal&lt;/CODE&gt; index, you can use the following search to find the tcpout connection targets for all forwarders:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal source=*metrics.log* group=tcpout_connections | chart values(destIp) by host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;hope this helps...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 11:05:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90106#M23102</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-10-09T11:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Find where a forwarder is forwarding too</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90107#M23103</link>
      <description>&lt;P&gt;This approach might work even if only the &lt;EM&gt;intermediate&lt;/EM&gt; forwarders are sending their &lt;CODE&gt;_internal&lt;/CODE&gt; index events; you'd see incoming connections from the various forwarders in the metrics.log.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 13:10:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90107#M23103</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-10-09T13:10:16Z</dc:date>
    </item>
    <item>
      <title>Re: Find where a forwarder is forwarding too</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90108#M23104</link>
      <description>&lt;P&gt;That does seem to bring a few up with the expected results but by no means all, do you have any further advice ?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 08:47:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90108#M23104</guid>
      <dc:creator>AaronMoorcroft</dc:creator>
      <dc:date>2013-10-10T08:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: Find where a forwarder is forwarding too</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90109#M23105</link>
      <description>&lt;P&gt;as I said, you need to have the forwarders _internal available. Another way would be to use the REST endpoint /data/outputs/tcp/ but again, this must be done against each forwarder. I would suggest to enable _internal forwarding this would also help in any case of troubleshooting future issues.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 09:02:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Find-where-a-forwarder-is-forwarding-too/m-p/90109#M23105</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-10-10T09:02:13Z</dc:date>
    </item>
  </channel>
</rss>

