<?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: Best practice for forwarding data into Splunk through an intermediate forwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283853#M54283</link>
    <description>&lt;P&gt;Rich is suggesting you receive syslog to something like rsyslog or syslog-ng. Write to file. Monitor the files with the Universal Forward and it sends to Splunk.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Feb 2017 02:36:05 GMT</pubDate>
    <dc:creator>starcher</dc:creator>
    <dc:date>2017-02-10T02:36:05Z</dc:date>
    <item>
      <title>Best practice for forwarding data into Splunk through an intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283850#M54280</link>
      <description>&lt;P&gt;I am seeking the best practice option to send data to my Splunk instance through an intermediate forwarder with emphasis on &lt;STRONG&gt;not&lt;/STRONG&gt; losing data. I use universal forwarders. The intermediate Forwarder is on a Syslog server.&lt;/P&gt;

&lt;P&gt;I currently put a forwarder on my hosts which send data to an intermediate forwarder which listens on a port, then sends the data to the Splunk Indexing cluster.     &lt;CODE&gt;Current Setup: Host(w/ forwarder) -&amp;gt; Intermediate Forwarder (listens TCP/UDP) -&amp;gt; Sends to Cluster&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;My question is: &lt;BR /&gt;
1Q: Any links/advice to setting up this configuration with emphasis on not losing the data?&lt;BR /&gt;
2Q: Should my setup be: &lt;CODE&gt;Host (w/ syslog-out) -&amp;gt; syslog_server -&amp;gt; Intermediate_forwarder (listen to syslog.log) -&amp;gt; Cluster&lt;/CODE&gt;&lt;BR /&gt;
3Q: Can this work? &lt;CODE&gt;Host (w/ forwarder) -&amp;gt; syslog_server -&amp;gt; Intermediate_forwarder(listen to syslog.log) -&amp;gt; cluster&lt;/CODE&gt;&lt;BR /&gt;
4Q: When I restart the host or forwarder, which is the best setup to not lose data?&lt;/P&gt;

&lt;P&gt;I've read quite a number of forum posts but I may have missed something. Thank You.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 21:35:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283850#M54280</guid>
      <dc:creator>rewritex</dc:creator>
      <dc:date>2017-02-09T21:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for forwarding data into Splunk through an intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283851#M54281</link>
      <description>&lt;P&gt;Intermediate forwarders are not considered Best Practice.  The preferred approach is to forward your syslogs to a syslog server then have a Universal Forwarder on the syslog server forward logs to your index cluster.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 22:23:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283851#M54281</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-02-09T22:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for forwarding data into Splunk through an intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283852#M54282</link>
      <description>&lt;P&gt;Thank you for the response. &lt;/P&gt;

&lt;P&gt;Concerning the &lt;STRONG&gt;host&lt;/STRONG&gt; setup best option.... can i use the universal forwarder to send data to the dedicate_syslog server or should I just syslog-out?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 23:18:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283852#M54282</guid>
      <dc:creator>rewritex</dc:creator>
      <dc:date>2017-02-09T23:18:35Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for forwarding data into Splunk through an intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283853#M54283</link>
      <description>&lt;P&gt;Rich is suggesting you receive syslog to something like rsyslog or syslog-ng. Write to file. Monitor the files with the Universal Forward and it sends to Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 02:36:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283853#M54283</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2017-02-10T02:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for forwarding data into Splunk through an intermediate forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283854#M54284</link>
      <description>&lt;P&gt;&lt;A href="http://www.function1.com/2012/05/syslog-collection-with-splunk"&gt;This article&lt;/A&gt; may help, in addition to the other responses you already received. &lt;BR /&gt;
Intermediary forwarders come with their own architectural pitfalls and you need to ensure that any intermediary forwarding tier is architected properly to not introduce single points of failure or cause event distribution issues across your indexers. Sometimes, network connectivity restrictions or other requirements make them necessary, but - like others have said - you shouldn't introduce any additional tiers in your forwarding architecture that are not needed. The KISS principle applies. &lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 17:59:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practice-for-forwarding-data-into-Splunk-through-an/m-p/283854#M54284</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2017-02-10T17:59:14Z</dc:date>
    </item>
  </channel>
</rss>

