<?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: universal forwarder props.conf? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61715#M12322</link>
    <description>&lt;P&gt;There are instances where you would have a props.conf on the UF but not for line breaking and timestamping. These tasks are done on the Indexer. &lt;/P&gt;

&lt;P&gt;One use case is for MSSQL logs because they are in a different UTF format so you would need to have a props.conf on the UF to let the UF know what format the data is in . &lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2013 19:27:16 GMT</pubDate>
    <dc:creator>tgow</dc:creator>
    <dc:date>2013-03-14T19:27:16Z</dc:date>
    <item>
      <title>universal forwarder props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61714#M12321</link>
      <description>&lt;P&gt;Should a props.conf even exist on universal forwarders? Is all that work (including timestamp and line-breaking) done at the indexer? &lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2013 18:45:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61714#M12321</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2013-03-14T18:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: universal forwarder props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61715#M12322</link>
      <description>&lt;P&gt;There are instances where you would have a props.conf on the UF but not for line breaking and timestamping. These tasks are done on the Indexer. &lt;/P&gt;

&lt;P&gt;One use case is for MSSQL logs because they are in a different UTF format so you would need to have a props.conf on the UF to let the UF know what format the data is in . &lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2013 19:27:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61715#M12322</guid>
      <dc:creator>tgow</dc:creator>
      <dc:date>2013-03-14T19:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: universal forwarder props.conf?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61716#M12323</link>
      <description>&lt;P&gt;Good resource &lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F"&gt;here&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;You can set things like the sourcetype in props.conf at the input stage - which is all the UF does (the input stage)&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2013 20:56:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/universal-forwarder-props-conf/m-p/61716#M12323</guid>
      <dc:creator>jonuwz</dc:creator>
      <dc:date>2013-03-14T20:56:32Z</dc:date>
    </item>
  </channel>
</rss>

