<?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: Timestamp extraction in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299572#M56667</link>
    <description>&lt;P&gt;Yes,&lt;/P&gt;

&lt;P&gt;In props.conf you can use the following:&lt;/P&gt;

&lt;P&gt;INDEXED_EXTRACTIONS = &amp;lt; CSV|W3C|TSV|PSV|JSON &amp;gt;&lt;BR /&gt;
* Tells Splunk the type of file and the extraction and/or parsing method&lt;BR /&gt;
  Splunk should use on the file.&lt;BR /&gt;
  CSV  - Comma separated value format&lt;BR /&gt;
  TSV  - Tab-separated value format&lt;BR /&gt;
  PSV  - pipe "|" separated value format&lt;BR /&gt;
  W3C  - W3C Extended Extended Log File Format&lt;BR /&gt;
  JSON - JavaScript Object Notation format&lt;BR /&gt;
* These settings default the values of the remaining settings to the&lt;BR /&gt;
  appropriate values for these known formats.&lt;BR /&gt;
* Defaults to unset.&lt;/P&gt;

&lt;P&gt;TIMESTAMP_FIELDS = [ ,..., ]&lt;BR /&gt;
* Some CSV and structured files have their timestamp encompass multiple&lt;BR /&gt;
  fields in the event separated by delimiters. This attribute tells Splunk to&lt;BR /&gt;
  specify all such fields which constitute the timestamp in a&lt;BR /&gt;
  comma-separated fashion.&lt;BR /&gt;
* If not specified, Splunk tries to automatically extract the timestamp of&lt;BR /&gt;
  the event.&lt;/P&gt;

&lt;P&gt;Note:&lt;BR /&gt;
* This feature and all of its settings apply at input time, when data is&lt;BR /&gt;
  first read by Splunk.  The setting is used on a Splunk system that has&lt;BR /&gt;
  configured inputs acquiring the data.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jul 2017 10:13:38 GMT</pubDate>
    <dc:creator>jkat54</dc:creator>
    <dc:date>2017-07-10T10:13:38Z</dc:date>
    <item>
      <title>Timestamp extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299570#M56665</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I've got a csv file with the a date field against events in the format 1-July-2016. Can I create a sourcetype to recognise this as the timestamp for this data set?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2017 09:23:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299570#M56665</guid>
      <dc:creator>pdjhh</dc:creator>
      <dc:date>2017-07-10T09:23:24Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299571#M56666</link>
      <description>&lt;P&gt;Hi pdjhh,&lt;BR /&gt;
yes this is the correct method.&lt;BR /&gt;
I suggest to use the web interface to find the correct format and sourcetype definition.&lt;BR /&gt;
With CSV you can set the time field in sourcetype definition.&lt;/P&gt;

&lt;P&gt;Anyway, your time format is &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;%d-%B-%Y
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Remeber that ingesting CSV inputs, you have to put props.conf on Indexers and also on Forwarders.&lt;/P&gt;

&lt;P&gt;Bye.&lt;/P&gt;

&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2017 09:28:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299571#M56666</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-07-10T09:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299572#M56667</link>
      <description>&lt;P&gt;Yes,&lt;/P&gt;

&lt;P&gt;In props.conf you can use the following:&lt;/P&gt;

&lt;P&gt;INDEXED_EXTRACTIONS = &amp;lt; CSV|W3C|TSV|PSV|JSON &amp;gt;&lt;BR /&gt;
* Tells Splunk the type of file and the extraction and/or parsing method&lt;BR /&gt;
  Splunk should use on the file.&lt;BR /&gt;
  CSV  - Comma separated value format&lt;BR /&gt;
  TSV  - Tab-separated value format&lt;BR /&gt;
  PSV  - pipe "|" separated value format&lt;BR /&gt;
  W3C  - W3C Extended Extended Log File Format&lt;BR /&gt;
  JSON - JavaScript Object Notation format&lt;BR /&gt;
* These settings default the values of the remaining settings to the&lt;BR /&gt;
  appropriate values for these known formats.&lt;BR /&gt;
* Defaults to unset.&lt;/P&gt;

&lt;P&gt;TIMESTAMP_FIELDS = [ ,..., ]&lt;BR /&gt;
* Some CSV and structured files have their timestamp encompass multiple&lt;BR /&gt;
  fields in the event separated by delimiters. This attribute tells Splunk to&lt;BR /&gt;
  specify all such fields which constitute the timestamp in a&lt;BR /&gt;
  comma-separated fashion.&lt;BR /&gt;
* If not specified, Splunk tries to automatically extract the timestamp of&lt;BR /&gt;
  the event.&lt;/P&gt;

&lt;P&gt;Note:&lt;BR /&gt;
* This feature and all of its settings apply at input time, when data is&lt;BR /&gt;
  first read by Splunk.  The setting is used on a Splunk system that has&lt;BR /&gt;
  configured inputs acquiring the data.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2017 10:13:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-extraction/m-p/299572#M56667</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-07-10T10:13:38Z</dc:date>
    </item>
  </channel>
</rss>

