<?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 props.conf extractions in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102264#M21454</link>
    <description>&lt;P&gt;I have a quick question here.  I have a distributed environment with about 5 indexers and then a main search head.  &lt;/P&gt;

&lt;P&gt;I have a props.conf file on 1 of the indexers and it's being used to extract data into fields.  However when searching on the main search head for this data, the fields aren't present.  If I search on the indexer itself where the props.conf resides, the fields are present.&lt;/P&gt;

&lt;P&gt;Do I have to put the extractions in the props.conf on the search head as well? I would have thought putting it on the indexer was the right thing to do and that this would filter down when searching on the main search head.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jul 2012 16:30:22 GMT</pubDate>
    <dc:creator>gnovak</dc:creator>
    <dc:date>2012-07-18T16:30:22Z</dc:date>
    <item>
      <title>props.conf extractions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102264#M21454</link>
      <description>&lt;P&gt;I have a quick question here.  I have a distributed environment with about 5 indexers and then a main search head.  &lt;/P&gt;

&lt;P&gt;I have a props.conf file on 1 of the indexers and it's being used to extract data into fields.  However when searching on the main search head for this data, the fields aren't present.  If I search on the indexer itself where the props.conf resides, the fields are present.&lt;/P&gt;

&lt;P&gt;Do I have to put the extractions in the props.conf on the search head as well? I would have thought putting it on the indexer was the right thing to do and that this would filter down when searching on the main search head.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2012 16:30:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102264#M21454</guid>
      <dc:creator>gnovak</dc:creator>
      <dc:date>2012-07-18T16:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf extractions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102265#M21455</link>
      <description>&lt;P&gt;Actually nevermind!  I put the extractions in the props.conf also on the search head and this resolved the issue.  No worries here!&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2012 16:33:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102265#M21455</guid>
      <dc:creator>gnovak</dc:creator>
      <dc:date>2012-07-18T16:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf extractions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102266#M21456</link>
      <description>&lt;P&gt;If you think about it, since Splunk does the field extractions at search time, and the search head has to coordinate and post-process the data coming from all the indexers, the search head must have all search-time knowledge objects.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2012 16:54:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-extractions/m-p/102266#M21456</guid>
      <dc:creator>Jon_Webster</dc:creator>
      <dc:date>2012-07-18T16:54:31Z</dc:date>
    </item>
  </channel>
</rss>

