<?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: Configuring inputs.conf to send data to specific Index in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Configuring-inputs-conf-to-send-data-to-specific-Index/m-p/207512#M40912</link>
    <description>&lt;P&gt;Presonally, I would try to stick to setting this at the Universal Forwarder if possible. I don't think there's a significant processing cost to routing at the other tiers, but once you have a larger environment I think it would be a hassle to figure out why events are ending up in various indexes. I guess my philosophy is that if something can be done on the UF, that's probably the way to go.&lt;/P&gt;

&lt;P&gt;That said, I probably wouldn't hesitate to select indexes on the HF or Indexer if I needed to make a change quickly and didn't have control of the UFs. If you ever want to select indexes based on something in the events themselves, such as the raw data, you're going to end up making that change on the HF or Indexer.&lt;/P&gt;

&lt;P&gt;Good luck!&lt;/P&gt;</description>
    <pubDate>Sat, 16 Apr 2016 15:58:35 GMT</pubDate>
    <dc:creator>jtacy</dc:creator>
    <dc:date>2016-04-16T15:58:35Z</dc:date>
    <item>
      <title>Configuring inputs.conf to send data to specific Index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configuring-inputs-conf-to-send-data-to-specific-Index/m-p/207511#M40911</link>
      <description>&lt;P&gt;I have a Splunk setup defined like: Universal Forwarder ----&amp;gt;Heavy Forwarder  ------&amp;gt;Indexer&lt;/P&gt;

&lt;P&gt;I need that all the logs hitting my Indexer should go to specific index. Which option is better:&lt;/P&gt;

&lt;P&gt;1) Configuring &lt;STRONG&gt;index= new_index&lt;/STRONG&gt; in Universal forwarder's input.conf&lt;BR /&gt;
2) Configuring &lt;STRONG&gt;index= new_index&lt;/STRONG&gt; in Heavy forwarder's input.conf&lt;BR /&gt;
3) Configuring &lt;STRONG&gt;index= new_index&lt;/STRONG&gt; in Indexer's input.conf&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2016 15:00:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configuring-inputs-conf-to-send-data-to-specific-Index/m-p/207511#M40911</guid>
      <dc:creator>splunk_kk</dc:creator>
      <dc:date>2016-04-16T15:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring inputs.conf to send data to specific Index</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configuring-inputs-conf-to-send-data-to-specific-Index/m-p/207512#M40912</link>
      <description>&lt;P&gt;Presonally, I would try to stick to setting this at the Universal Forwarder if possible. I don't think there's a significant processing cost to routing at the other tiers, but once you have a larger environment I think it would be a hassle to figure out why events are ending up in various indexes. I guess my philosophy is that if something can be done on the UF, that's probably the way to go.&lt;/P&gt;

&lt;P&gt;That said, I probably wouldn't hesitate to select indexes on the HF or Indexer if I needed to make a change quickly and didn't have control of the UFs. If you ever want to select indexes based on something in the events themselves, such as the raw data, you're going to end up making that change on the HF or Indexer.&lt;/P&gt;

&lt;P&gt;Good luck!&lt;/P&gt;</description>
      <pubDate>Sat, 16 Apr 2016 15:58:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configuring-inputs-conf-to-send-data-to-specific-Index/m-p/207512#M40912</guid>
      <dc:creator>jtacy</dc:creator>
      <dc:date>2016-04-16T15:58:35Z</dc:date>
    </item>
  </channel>
</rss>

