<?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 Best Practice for Getting Data from Splunk Instances Into Indexer Cluster in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691302#M114987</link>
    <description>&lt;P&gt;I have the following setup with Indexer Discovery + Indexer Cluster + Search Head Cluster:&lt;/P&gt;&lt;P&gt;- Deployment Server&lt;/P&gt;&lt;P&gt;- 3 X Indexer + Cluster Manager (Indexer Cluster)&lt;/P&gt;&lt;P&gt;- Search Head Deployer + Search Head (Set-up as part of a SHC for possible future scaling up)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For forwarding logs from &lt;STRONG&gt;Cluster Manager&lt;/STRONG&gt;, I referred to:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/Indexer/Forwardmanagerdata" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Forwardmanagerdata&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For forwarding logs from &lt;STRONG&gt;Search Head Cluster&lt;/STRONG&gt; nodes, I referred to:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe forwarding logs from the &lt;STRONG&gt;Deployment Server&lt;/STRONG&gt; should be similar to the above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For &lt;STRONG&gt;indexers&lt;/STRONG&gt; belonging to an &lt;STRONG&gt;indexer cluster&lt;/STRONG&gt;, I have considered the following:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; Install UF in each indexer to monitor &amp;amp; forward logs to the indexer cluster (via indexer discovery)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.&lt;/STRONG&gt; Just monitor logs locally and allow each indexer to index its own local logs (without going through the indexer cluster)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3.&lt;/STRONG&gt; Configure the indexer to forward the locally monitored logs without indexing, to the indexer cluster. I am not sure if is necessary to ensure that it does not index the same data twice. Unsure on how this would play out.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 2&lt;/STRONG&gt; seems to be the easiest to achieve, but ideally I would like all logs to go through the indexer cluster for indexing.&lt;/P&gt;&lt;P&gt;What should be the best practice for forwarding logs from indexers that are part of the indexer cluster?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 13:55:09 GMT</pubDate>
    <dc:creator>Fortron</dc:creator>
    <dc:date>2024-06-21T13:55:09Z</dc:date>
    <item>
      <title>Best Practice for Getting Data from Splunk Instances Into Indexer Cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691302#M114987</link>
      <description>&lt;P&gt;I have the following setup with Indexer Discovery + Indexer Cluster + Search Head Cluster:&lt;/P&gt;&lt;P&gt;- Deployment Server&lt;/P&gt;&lt;P&gt;- 3 X Indexer + Cluster Manager (Indexer Cluster)&lt;/P&gt;&lt;P&gt;- Search Head Deployer + Search Head (Set-up as part of a SHC for possible future scaling up)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For forwarding logs from &lt;STRONG&gt;Cluster Manager&lt;/STRONG&gt;, I referred to:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/Indexer/Forwardmanagerdata" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Forwardmanagerdata&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For forwarding logs from &lt;STRONG&gt;Search Head Cluster&lt;/STRONG&gt; nodes, I referred to:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe forwarding logs from the &lt;STRONG&gt;Deployment Server&lt;/STRONG&gt; should be similar to the above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For &lt;STRONG&gt;indexers&lt;/STRONG&gt; belonging to an &lt;STRONG&gt;indexer cluster&lt;/STRONG&gt;, I have considered the following:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; Install UF in each indexer to monitor &amp;amp; forward logs to the indexer cluster (via indexer discovery)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.&lt;/STRONG&gt; Just monitor logs locally and allow each indexer to index its own local logs (without going through the indexer cluster)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3.&lt;/STRONG&gt; Configure the indexer to forward the locally monitored logs without indexing, to the indexer cluster. I am not sure if is necessary to ensure that it does not index the same data twice. Unsure on how this would play out.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Option 2&lt;/STRONG&gt; seems to be the easiest to achieve, but ideally I would like all logs to go through the indexer cluster for indexing.&lt;/P&gt;&lt;P&gt;What should be the best practice for forwarding logs from indexers that are part of the indexer cluster?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 13:55:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691302#M114987</guid>
      <dc:creator>Fortron</dc:creator>
      <dc:date>2024-06-21T13:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for Getting Data from Splunk Instances Into Indexer Cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691315#M114988</link>
      <description>&lt;P&gt;While most instance types should forward their logs to the indexers (using outputs.conf), indexers must not do so lest they cause an infinite loop.&amp;nbsp; By virtue of the fact the indexer is part of the cluster, its logs go through the cluster.&lt;/P&gt;&lt;P&gt;What problem are you trying to solve?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 16:51:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691315#M114988</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-06-21T16:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for Getting Data from Splunk Instances Into Indexer Cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691317#M114989</link>
      <description>&lt;P&gt;I believe it is due to my lack of understanding on how the indexers in an indexer cluster treat locally monitored data versus data forwarded to the indexer cluster. I mistakenly thought that locally monitored logs on each indexer don't get treated the same way as logs that were forwarded to the indexer cluster.&lt;BR /&gt;&lt;BR /&gt;Thank you for pointing out on the infinite loop, I guess this was the issue when I tried to configure the indexer to forward locally monitored data to its own indexer cluster, which made them spew out alot of errors.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In that case it seems that I should just create an `inputs.conf` on the indexers and monitor whatever I want, as the indexers' logs would get indexed and subsequently replicated, if I'm understanding it correctly.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thank you for your help!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 17:10:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-Practice-for-Getting-Data-from-Splunk-Instances-Into/m-p/691317#M114989</guid>
      <dc:creator>Fortron</dc:creator>
      <dc:date>2024-06-21T17:10:52Z</dc:date>
    </item>
  </channel>
</rss>

