<?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: Does a universal forwarder ever read props.conf? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198758#M39397</link>
    <description>&lt;P&gt;It appears that you need to edit the props.conf file on the &lt;EM&gt;forwarder&lt;/EM&gt; if you want to have non-default handling of structured (e.g. CSV files).  &lt;/P&gt;

&lt;P&gt;In particular, I was trying to have a CSV file override the timestamp field to read it from one of my fields -- I needed to tell the fowarder that it was a custom type:&lt;/P&gt;

&lt;P&gt;Forwarder:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[myType] &lt;BR /&gt;
INDEXED_EXTRACTIONS = csv&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;And on the indexer:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[myType] &lt;BR /&gt;
INDEXED_EXTRACTIONS = csv&lt;BR /&gt;
TIMESTAMP_FIELDS = foo&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;If only the second one was set, the events did not parse correctly.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 07:24:56 GMT</pubDate>
    <dc:creator>gbronner_rbc</dc:creator>
    <dc:date>2020-09-29T07:24:56Z</dc:date>
    <item>
      <title>Does a universal forwarder ever read props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198754#M39393</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Does a UFW ever read a props.conf file?  Is there any reason to put a props.conf on a UFW system? &lt;/P&gt;</description>
      <pubDate>Sat, 30 Aug 2014 22:40:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198754#M39393</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2014-08-30T22:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: Does a universal forwarder ever read props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198755#M39394</link>
      <description>&lt;P&gt;Yes it does. See &lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt; under "inputs".&lt;/P&gt;</description>
      <pubDate>Sun, 31 Aug 2014 01:14:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198755#M39394</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2014-08-31T01:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: Does a universal forwarder ever read props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198756#M39395</link>
      <description>&lt;P&gt;? That is not how I understand the process to happen or even what I read from what you linked. A UF has no concept of what an event is. However you can set things like the host and sourcetype fields and what index data goes to. You can't do things like control linebreaking, timestamp definition, etc which are set in props.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2014 09:52:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198756#M39395</guid>
      <dc:creator>Runals</dc:creator>
      <dc:date>2014-09-02T09:52:37Z</dc:date>
    </item>
    <item>
      <title>Re: Does a universal forwarder ever read props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198757#M39396</link>
      <description>&lt;P&gt;See &lt;A href="http://wiki.splunk.com/Community:HowIndexingWorks"&gt;http://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt; for a summary of which settings take effect at which locations.&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2015 13:41:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198757#M39396</guid>
      <dc:creator>cphair</dc:creator>
      <dc:date>2015-05-07T13:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: Does a universal forwarder ever read props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198758#M39397</link>
      <description>&lt;P&gt;It appears that you need to edit the props.conf file on the &lt;EM&gt;forwarder&lt;/EM&gt; if you want to have non-default handling of structured (e.g. CSV files).  &lt;/P&gt;

&lt;P&gt;In particular, I was trying to have a CSV file override the timestamp field to read it from one of my fields -- I needed to tell the fowarder that it was a custom type:&lt;/P&gt;

&lt;P&gt;Forwarder:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[myType] &lt;BR /&gt;
INDEXED_EXTRACTIONS = csv&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;And on the indexer:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[myType] &lt;BR /&gt;
INDEXED_EXTRACTIONS = csv&lt;BR /&gt;
TIMESTAMP_FIELDS = foo&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;If only the second one was set, the events did not parse correctly.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:24:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-universal-forwarder-ever-read-props-conf/m-p/198758#M39397</guid>
      <dc:creator>gbronner_rbc</dc:creator>
      <dc:date>2020-09-29T07:24:56Z</dc:date>
    </item>
  </channel>
</rss>

