<?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: Problem with routing/forwarding to a specific index. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33332#M5960</link>
    <description>&lt;P&gt;OK, I got the central forwarder fixed. I had to add the line &lt;CODE&gt;index = windows&lt;/CODE&gt; to &lt;CODE&gt;%SPLUNK_HOME\etc\system\local\inputs.conf&lt;/CODE&gt; and removed &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkForwarder\local\inputs.conf&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 21 Aug 2010 01:18:41 GMT</pubDate>
    <dc:creator>aaronzabell</dc:creator>
    <dc:date>2010-08-21T01:18:41Z</dc:date>
    <item>
      <title>Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33327#M5955</link>
      <description>&lt;P&gt;I have a bunch of light forwarders sending data to a central heavy forwarder which then sends the data to the main indexer.&lt;/P&gt;

&lt;P&gt;On the central heavy forwarder and the main indexer I've created an index called &lt;CODE&gt;windows&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;When I run a search on the main indexer, it doesn't look like all of the data is going into the &lt;CODE&gt;windows&lt;/CODE&gt; index and I don't know why. In particular one Windows 7 Professional system (a light forwarder) and a Windows XP Pro system (the central heavy forwarder). The other systems are getting forwarded just fine (They consist of Win 2000, XP, Server 2003 and Server 2008 R2). Help?&lt;/P&gt;

&lt;P&gt;On each light forwarder Ive placed &lt;CODE&gt;inputs.conf&lt;/CODE&gt; in: &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkLightForwarder\local\inputs.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
index = windows
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;On the central heavy forwarder I've placed the inputs.conf in: &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkForwarder\local\inputs.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
index = windows
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 19 Aug 2010 04:14:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33327#M5955</guid>
      <dc:creator>aaronzabell</dc:creator>
      <dc:date>2010-08-19T04:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33328#M5956</link>
      <description>&lt;P&gt;that's generally the right way, except that any particular input can override the default and send its data to a different index, and transforms can also change the target index.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Aug 2010 10:43:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33328#M5956</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-08-19T10:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33329#M5957</link>
      <description>&lt;P&gt;So on those 2 systems do you think placing the &lt;CODE&gt;inputs.conf&lt;/CODE&gt; in &lt;CODE&gt;%SPLUNK_HOME\etc\system\local&lt;/CODE&gt; will do the trick?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2010 10:03:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33329#M5957</guid>
      <dc:creator>aaronzabell</dc:creator>
      <dc:date>2010-08-20T10:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33330#M5958</link>
      <description>&lt;P&gt;No I am saying that the specific input can set a different index so your default may be overridden.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2010 14:59:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33330#M5958</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-08-20T14:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33331#M5959</link>
      <description>&lt;P&gt;OK, any idea as to why these 2 systems aren't cooperating then?&lt;/P&gt;</description>
      <pubDate>Sat, 21 Aug 2010 01:09:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33331#M5959</guid>
      <dc:creator>aaronzabell</dc:creator>
      <dc:date>2010-08-21T01:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33332#M5960</link>
      <description>&lt;P&gt;OK, I got the central forwarder fixed. I had to add the line &lt;CODE&gt;index = windows&lt;/CODE&gt; to &lt;CODE&gt;%SPLUNK_HOME\etc\system\local\inputs.conf&lt;/CODE&gt; and removed &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkForwarder\local\inputs.conf&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 21 Aug 2010 01:18:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33332#M5960</guid>
      <dc:creator>aaronzabell</dc:creator>
      <dc:date>2010-08-21T01:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with routing/forwarding to a specific index.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33333#M5961</link>
      <description>&lt;P&gt;Well, apparently on the 2 problem systems, this is the solution:
I had to add the line&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;index = windows&lt;/CODE&gt; to&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;%SPLUNK_HOME\etc\system\local\inputs.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;P&gt;removed &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkForwarder\local\inputs.conf&lt;/CODE&gt; (on the central heavy forwarder)&lt;/P&gt;

&lt;P&gt;removed &lt;CODE&gt;%SPLUNK_HOME\etc\apps\SplunkLightForwarder\local\inputs.conf&lt;/CODE&gt; (on the Windows 7 light forwarder)&lt;/P&gt;

&lt;P&gt;I still have no clue why it needed to be different for these 2 systems.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Aug 2010 01:29:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-with-routing-forwarding-to-a-specific-index/m-p/33333#M5961</guid>
      <dc:creator>aaronzabell</dc:creator>
      <dc:date>2010-08-21T01:29:29Z</dc:date>
    </item>
  </channel>
</rss>

