<?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: _time improper format in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317075#M162652</link>
    <description>&lt;P&gt;It would also be good to specify &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt;and &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; so splunk knows where the timestamp is located &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype_name]
TIME_PREFIX = ^
TIME_FORMAT = %d-%m-%Y %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 20
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 01 Mar 2018 19:38:20 GMT</pubDate>
    <dc:creator>skoelpin</dc:creator>
    <dc:date>2018-03-01T19:38:20Z</dc:date>
    <item>
      <title>_time improper format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317073#M162650</link>
      <description>&lt;P&gt;Hello splunkers,&lt;/P&gt;

&lt;P&gt;I have logs in my file &lt;BR /&gt;
01-03-2018 15:54:58 WARNING [PID:88888][TradeId:11551427] /apps/abcrc/src/check/src/mx_rtpr.cpp:1146 - Sanity Check Exception void sanity_check(void*, rtPRICING_API_LIBRARY*)@/apps/abcrc/Flex/src/mx_rtpr.cpp:1034:End date not equal to option expiry date&lt;/P&gt;

&lt;P&gt;that log is of 1st march 2018 but splunk has taken it as a log of 3 January 2018 , please suggest how to manipulate _time field so that my new data or existing data will come in proper time format .&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:13:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317073#M162650</guid>
      <dc:creator>kannu</dc:creator>
      <dc:date>2020-09-29T18:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: _time improper format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317074#M162651</link>
      <description>&lt;P&gt;Include &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; in props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype_name]
TIME_FORMAT = %d-%m-%Y %H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 01 Mar 2018 17:07:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317074#M162651</guid>
      <dc:creator>493669</dc:creator>
      <dc:date>2018-03-01T17:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: _time improper format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317075#M162652</link>
      <description>&lt;P&gt;It would also be good to specify &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt;and &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; so splunk knows where the timestamp is located &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype_name]
TIME_PREFIX = ^
TIME_FORMAT = %d-%m-%Y %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 20
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 01 Mar 2018 19:38:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/time-improper-format/m-p/317075#M162652</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2018-03-01T19:38:20Z</dc:date>
    </item>
  </channel>
</rss>

