<?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: Unusual date parsing. in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112393#M29527</link>
    <description>&lt;P&gt;I haven't used it in production but it works in Data prewiev wizard. Did you try with it? Maybe try playing with MAX_TIMESTAMP_LOOKAHEAD setting (set it to 17)?&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 15:39:28 GMT</pubDate>
    <dc:creator>MaverickT</dc:creator>
    <dc:date>2020-09-28T15:39:28Z</dc:date>
    <item>
      <title>Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112390#M29524</link>
      <description>&lt;P&gt;Is it possible to have splunk parse the following date format? Year-Day-Hour_minute_Second&lt;/P&gt;

&lt;P&gt;i.e. 2008-265-03:19:26 would be 2008/09/22 at 3:19:26.&lt;/P&gt;

&lt;P&gt;What I want to do is make graphs based on the time in my data, and not based on the timestamp of my log files. Right now the time field is extracted but I don't know how to work with it.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:38:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112390#M29524</guid>
      <dc:creator>dcollette</dc:creator>
      <dc:date>2020-09-28T15:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112391#M29525</link>
      <description>&lt;P&gt;Ofcourse, this is the timeformat you should use for extraction:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;%Y-%j-%H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Jan 2014 13:32:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112391#M29525</guid>
      <dc:creator>MaverickT</dc:creator>
      <dc:date>2014-01-14T13:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112392#M29526</link>
      <description>&lt;P&gt;I put the following into a props.config file.&lt;/P&gt;

&lt;P&gt;[source::"nameoffile"]&lt;BR /&gt;
TIME_FORMAT = %Y-%j-%H:%M:%S&lt;/P&gt;

&lt;P&gt;It is still resolving to the default file timestamp. Any ideas?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2014 18:05:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112392#M29526</guid>
      <dc:creator>dcollette</dc:creator>
      <dc:date>2014-01-14T18:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112393#M29527</link>
      <description>&lt;P&gt;I haven't used it in production but it works in Data prewiev wizard. Did you try with it? Maybe try playing with MAX_TIMESTAMP_LOOKAHEAD setting (set it to 17)?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:39:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112393#M29527</guid>
      <dc:creator>MaverickT</dc:creator>
      <dc:date>2020-09-28T15:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112394#M29528</link>
      <description>&lt;P&gt;Also if your timestamp doesn't start from the very beginning of the line, you need to provide the TIME_PREFIX property, which is a regex for everything that precedes the timestamp.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2014 22:59:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112394#M29528</guid>
      <dc:creator>Leo</dc:creator>
      <dc:date>2014-01-16T22:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Unusual date parsing.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112395#M29529</link>
      <description>&lt;P&gt;If you are talking about a field in your data that you want to use as a timestamp for charts, then you do Not want to use props.conf.  This document will tell you how to deal with time manipulation in a search:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/SearchReference/convert"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.1/SearchReference/convert&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;From the sounds of it, you want to use &lt;CODE&gt;mktime&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2014 00:17:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unusual-date-parsing/m-p/112395#M29529</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-01-17T00:17:36Z</dc:date>
    </item>
  </channel>
</rss>

