<?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: AM PM being ignored by TIME_FORMAT in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69371#M14055</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Two things that MAY improve the situation: &lt;/P&gt;

&lt;P&gt;a) Set the &lt;CODE&gt;TIME_PREFIX = ^\d+,&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;b) Set the &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD=18&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I have seen (on strftime.net) that &lt;CODE&gt;%l&lt;/CODE&gt; (lowercase L) should be the 12-hour format without leading zeroes. Other sources claim that &lt;CODE&gt;%I&lt;/CODE&gt; allows optional leading zeroes. Unfortunately I haven't found a definite list of the supported strftime/strptime formatting that Splunk accepts/recognizes.&lt;/P&gt;

&lt;P&gt;Also, on a side note, I don't think you need the filter for the parsing queue, since that is the default. You only need to filter out the header row to the null queue.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
    <pubDate>Tue, 25 Sep 2012 08:13:55 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2012-09-25T08:13:55Z</dc:date>
    <item>
      <title>AM PM being ignored by TIME_FORMAT in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69370#M14054</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;Having an issue importing the following data.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;UID, In Date, Update Time, Vol, Corr Vol
453,May 1 2012 6:00AM,May 2 2012 3:24PM,133,223.000000000
453,May 1 2012 7:00AM,May 2 2012 3:24PM,104,175.000000000
453,May 1 2012 8:00AM,May 2 2012 3:24PM,90,152.000000000
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[Flow]
KV_MODE = none
SHOULD_LINEMERGE = false
TIME_FORMAT = %b %d %Y %I:%M%p
TRANSFORMS-filterprices = filterFlowData, filterFlowHeaderRow
REPORT-extracts = FlowDataCsvExtract
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[filterFlowHeaderRow]
REGEX = ^UID(.*)
DEST_KEY = queue
FORMAT = nullQueue

[filterFlowData]
REGEX = (.*)
DEST_KEY = queue
FORMAT = indexQueue

[FlowDataCsvExtract]
DELIMS = ","
FIELDS = "UID", "In Date", "Update Time", "Vol", "Corr Vol"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It appears Splunk is retrieving the first time but completely ignoring the AM PM even though I am specifying it with the %p argument.&lt;/P&gt;

&lt;P&gt;Anyone have any clues how to persuade Splunk to not stop parsing the date too soon?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 05:06:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69370#M14054</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2012-09-25T05:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: AM PM being ignored by TIME_FORMAT in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69371#M14055</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Two things that MAY improve the situation: &lt;/P&gt;

&lt;P&gt;a) Set the &lt;CODE&gt;TIME_PREFIX = ^\d+,&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;b) Set the &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD=18&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I have seen (on strftime.net) that &lt;CODE&gt;%l&lt;/CODE&gt; (lowercase L) should be the 12-hour format without leading zeroes. Other sources claim that &lt;CODE&gt;%I&lt;/CODE&gt; allows optional leading zeroes. Unfortunately I haven't found a definite list of the supported strftime/strptime formatting that Splunk accepts/recognizes.&lt;/P&gt;

&lt;P&gt;Also, on a side note, I don't think you need the filter for the parsing queue, since that is the default. You only need to filter out the header row to the null queue.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 08:13:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69371#M14055</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-09-25T08:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: AM PM being ignored by TIME_FORMAT in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69372#M14056</link>
      <description>&lt;P&gt;Thanks for the tip it seems the TIME_PREFIX did the trick and its picking up the AM PM now.&lt;/P&gt;

&lt;P&gt;I tested both %I and %l (lowercase L) and both behaved in the same manner.&lt;/P&gt;

&lt;P&gt;Good to know about the filter as well. Nothing better than simplifying things.&lt;/P&gt;

&lt;P&gt;Thanks again&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 20:30:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AM-PM-being-ignored-by-TIME-FORMAT-in-props-conf/m-p/69372#M14056</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2012-09-25T20:30:55Z</dc:date>
    </item>
  </channel>
</rss>

