<?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: Assign sequential timestamps to data on data load in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101543#M21287</link>
    <description>&lt;P&gt;I don't recall specifying or overriding any default for the timestamp format, but here's some info:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
$ echo $OSTYPE&lt;BR /&gt;
linux-gnu&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;$ date&lt;BR /&gt;
Mon Jul 22 15:01:50 PDT 2013&lt;BR /&gt;
&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jul 2013 22:05:48 GMT</pubDate>
    <dc:creator>NK_1</dc:creator>
    <dc:date>2013-07-22T22:05:48Z</dc:date>
    <item>
      <title>Assign sequential timestamps to data on data load</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101540#M21284</link>
      <description>&lt;P&gt;I tried loading a textfile (via "splunk add oneshot datafile.txt") containing just IP addresses into Splunk v5.0, and Splunk tried to assign some really strange timestamps (2010 - 2019?) to some of those IP Address lines.&lt;BR /&gt;&lt;BR /&gt;
I suspect it tried to interpret some of the the ip address numbers as dates:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
$ grep DateParserVerbose ./var/log/splunk/splunkd.log | grep 2019&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;07-16-2013 17:31:16.085 -0700 WARN  DateParserVerbose - Accepted time (Sun Nov 24 19:11:24 2019) is suspiciously far away from the previous event's time (Sun Nov 21 12:33:24 2010), but still accepted because it was extracted by the same pattern. Context: source::(filename.csv)|host::(hostname)|(filename)|&lt;/P&gt;

&lt;P&gt;07-16-2013 17:31:16.085 -0700 WARN  DateParserVerbose - A possible timestamp match (Sun Nov 24 19:11:24 2019) is outside of the acceptable time window. If this timestamp is correct, consider adjusting MAX_DAYS_AGO and MAX_DAYS_HENCE. Context: source::(filename.csv)|host::(hostname)|(filename)|&lt;BR /&gt;
&lt;/P&gt;

&lt;P&gt;Is there a way to make Splunk assign sequential timestamps and not try to parse a timestamp from the data?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:23:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101540#M21284</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2020-09-28T14:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: Assign sequential timestamps to data on data load</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101541#M21285</link>
      <description>&lt;P&gt;I ended up doing this to prevent Splunk from guessing timestamps for now, but I'm looking for a better solution:&lt;BR /&gt;
&lt;PRE&gt;# add timestamp and key to every line in text file &lt;BR /&gt;
cat datafile.txt | xargs -d"\n" -I {} date +"%Y.%m.%d %H:%M:%S.%N ip={}" &amp;gt; datafile1.txt&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Jul 2013 02:22:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101541#M21285</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2013-07-20T02:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: Assign sequential timestamps to data on data load</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101542#M21286</link>
      <description>&lt;P&gt;If Splunk does not find a timestamp for each line contained into a file, the timestamp of the file creation will be used asvthe event timestamp. What is the timestamp format of your operation system? Tks!&lt;/P&gt;</description>
      <pubDate>Sat, 20 Jul 2013 03:08:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101542#M21286</guid>
      <dc:creator>wagnerbianchi</dc:creator>
      <dc:date>2013-07-20T03:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: Assign sequential timestamps to data on data load</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101543#M21287</link>
      <description>&lt;P&gt;I don't recall specifying or overriding any default for the timestamp format, but here's some info:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
$ echo $OSTYPE&lt;BR /&gt;
linux-gnu&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;$ date&lt;BR /&gt;
Mon Jul 22 15:01:50 PDT 2013&lt;BR /&gt;
&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2013 22:05:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Assign-sequential-timestamps-to-data-on-data-load/m-p/101543#M21287</guid>
      <dc:creator>NK_1</dc:creator>
      <dc:date>2013-07-22T22:05:48Z</dc:date>
    </item>
  </channel>
</rss>

