<?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: Indexing capability in Heavy forwarder and Indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-capability-in-Heavy-forwarder-and-Indexer/m-p/199205#M39455</link>
    <description>&lt;P&gt;You won't need the props.conf and transforms.conf in indexer if you are already parsing the data from heavy forwarder if that is the final data you want. Indexer will take as it is and index them. &lt;/P&gt;

&lt;P&gt;incase your indexer is not reachable then you may also set persistent queue option. &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 26 Mar 2014 05:25:26 GMT</pubDate>
    <dc:creator>linu1988</dc:creator>
    <dc:date>2014-03-26T05:25:26Z</dc:date>
    <item>
      <title>Indexing capability in Heavy forwarder and Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-capability-in-Heavy-forwarder-and-Indexer/m-p/199204#M39454</link>
      <description>&lt;P&gt;I would like to know the duty of the heavy forwarder and Indexer.&lt;BR /&gt;
My inputs is syslog data which is read by heavy forwarder. I had set &lt;STRONG&gt;props.conf&lt;/STRONG&gt;, &lt;STRONG&gt;transforms.conf&lt;/STRONG&gt; in heavy forwarder itself also in &lt;STRONG&gt;outputs.conf&lt;/STRONG&gt; I set the attribute ,&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;indexAndForward = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;this will index the data locally and forward parsed data to my indexer. &lt;BR /&gt;What will my indexer do ?&lt;BR /&gt;Will it just receive the indexed data and store in it mentioned index ?&lt;BR /&gt;&lt;BR /&gt;
What is the effect of mentioning my props.conf , transforms.conf in my indexer also?&lt;BR /&gt;&lt;/P&gt;

&lt;P&gt;My intension of using Heavy forwarder is to temporarily store the data and forward ,in case if my indexer is down or not-reachabale by forwarder. &lt;/P&gt;

&lt;P&gt;Please clarify what is the exact conf files i need to concentrate&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 03:32:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-capability-in-Heavy-forwarder-and-Indexer/m-p/199204#M39454</guid>
      <dc:creator>username021</dc:creator>
      <dc:date>2014-03-26T03:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing capability in Heavy forwarder and Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-capability-in-Heavy-forwarder-and-Indexer/m-p/199205#M39455</link>
      <description>&lt;P&gt;You won't need the props.conf and transforms.conf in indexer if you are already parsing the data from heavy forwarder if that is the final data you want. Indexer will take as it is and index them. &lt;/P&gt;

&lt;P&gt;incase your indexer is not reachable then you may also set persistent queue option. &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 05:25:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-capability-in-Heavy-forwarder-and-Indexer/m-p/199205#M39455</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2014-03-26T05:25:26Z</dc:date>
    </item>
  </channel>
</rss>

