<?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: how to sett forwarers to index on path and file name in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25752#M4218</link>
    <description>&lt;P&gt;Thanks for that pointer, but I am not sure that is what I was really asking. The logs all go into one index but have the extra tags for cluster and host added by the forwarder.&lt;/P&gt;

&lt;P&gt;I could set up forwarders for each "log type". These should be able to add tags for the cluster and host and read all files of that log type under /home/info/data/logs/*/.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Apr 2012 18:31:18 GMT</pubDate>
    <dc:creator>jbirchall1</dc:creator>
    <dc:date>2012-04-12T18:31:18Z</dc:date>
    <item>
      <title>how to sett forwarers to index on path and file name</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25750#M4216</link>
      <description>&lt;P&gt;Is it possible to set up forwarders to index data on the path of the file and a portion of the file name automatically. &lt;/P&gt;

&lt;P&gt;Ie &lt;/P&gt;

&lt;P&gt;/home/info/data/logs/"cluster"/host1.type1.log&lt;BR /&gt;
/home/info/data/logs/"cluster"/host2.type2.log&lt;/P&gt;

&lt;P&gt;The setup should automatically forward any files under /home/info/data/logs and add indexes for the "cluster" and the host? Any pointers in the right direction would be helpfull&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2012 17:07:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25750#M4216</guid>
      <dc:creator>jbirchall1</dc:creator>
      <dc:date>2012-04-12T17:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: how to sett forwarers to index on path and file name</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25751#M4217</link>
      <description>&lt;P&gt;You'd need to set up props/transforms where the data is being parsed(heavy forwarder/Indexer) to route data to specific indexes based on a regex:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/admin/Setupmultipleindexes#Route_specific_events_to_a_different_index"&gt;http://docs.splunk.com/Documentation/Splunk/latest/admin/Setupmultipleindexes#Route_specific_events_to_a_different_index&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2012 18:08:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25751#M4217</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2012-04-12T18:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: how to sett forwarers to index on path and file name</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25752#M4218</link>
      <description>&lt;P&gt;Thanks for that pointer, but I am not sure that is what I was really asking. The logs all go into one index but have the extra tags for cluster and host added by the forwarder.&lt;/P&gt;

&lt;P&gt;I could set up forwarders for each "log type". These should be able to add tags for the cluster and host and read all files of that log type under /home/info/data/logs/*/.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2012 18:31:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-sett-forwarers-to-index-on-path-and-file-name/m-p/25752#M4218</guid>
      <dc:creator>jbirchall1</dc:creator>
      <dc:date>2012-04-12T18:31:18Z</dc:date>
    </item>
  </channel>
</rss>

