<?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: Why is timestamp not selecting proper field in syslog data after upgrade to 7.3.3? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-timestamp-not-selecting-proper-field-in-syslog-data-after/m-p/503045#M85688</link>
    <description>&lt;P&gt;Try removing the blank &lt;CODE&gt;DATETIME_CONFIG =&lt;/CODE&gt; setting.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Dec 2019 17:29:17 GMT</pubDate>
    <dc:creator>FrankVl</dc:creator>
    <dc:date>2019-12-10T17:29:17Z</dc:date>
    <item>
      <title>Why is timestamp not selecting proper field in syslog data after upgrade to 7.3.3?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-timestamp-not-selecting-proper-field-in-syslog-data-after/m-p/503044#M85687</link>
      <description>&lt;P&gt;My data is from a command system that is being sent over UDP connection direct to the indexer.  It sends data to Splunk every hour. &lt;BR /&gt;
Data format is Month Date Time sent from command system,  system name, 1, Logon Time&lt;BR /&gt;
Examples&lt;BR /&gt;
Dec 10 00:51:46 system.network.net 1 2019-12-10T00:51:19.188-06:00&lt;BR /&gt;
Dec  9 10:58:25 system.netework.net 1 2019-12-09T10:58:23.793-06:00&lt;BR /&gt;
Dec  9 22:38:38 system.network.net 1 2019-12-06T08:05:23.745-06:00&lt;/P&gt;

&lt;P&gt;I want to use Logon Time as the event time not the time it was received.&lt;BR /&gt;&lt;BR /&gt;
This used to work until I upgraded to 7.3.3 from 7.3.0 to fix the Y2K20 issue.   &lt;/P&gt;

&lt;P&gt;props file contains &lt;BR /&gt;
DATETIME_CONFIG = &lt;BR /&gt;
LINE_BREAKER = ([\r\n]+)&lt;BR /&gt;
NO_BINARY_CHECK = true&lt;BR /&gt;
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3Q%:z&lt;BR /&gt;
TIME_PREFIX = \w+\s{1,}\d{1,}\s\d{2}:\d{2}:\d{2}\s\S+\s\d\s&lt;BR /&gt;
category = Custom&lt;BR /&gt;
disabled = false&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD = 256&lt;BR /&gt;
TIMESTAMP_FIELDS = &lt;/P&gt;

&lt;P&gt;Any suggestions on what happened?&lt;/P&gt;

&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:18:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-timestamp-not-selecting-proper-field-in-syslog-data-after/m-p/503044#M85687</guid>
      <dc:creator>scottrunyon</dc:creator>
      <dc:date>2020-09-30T03:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: Why is timestamp not selecting proper field in syslog data after upgrade to 7.3.3?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-timestamp-not-selecting-proper-field-in-syslog-data-after/m-p/503045#M85688</link>
      <description>&lt;P&gt;Try removing the blank &lt;CODE&gt;DATETIME_CONFIG =&lt;/CODE&gt; setting.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2019 17:29:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-timestamp-not-selecting-proper-field-in-syslog-data-after/m-p/503045#M85688</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2019-12-10T17:29:17Z</dc:date>
    </item>
  </channel>
</rss>

