<?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: Splunk date going backwards? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439240#M76587</link>
    <description>&lt;P&gt;By default, Splunk displays the most recent events first.  That's why dates appear to be going backwards.&lt;/P&gt;

&lt;P&gt;However, you appear to have an odd timestamp format in your events.  To ensure Splunk processes them properly and as a Best Practice, you should add the following to the [syslog] stanza of the appropriate props.conf file&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = &amp;gt;
TIME_FORMAT = %Y:%m%;d-%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 19
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sun, 05 May 2019 17:14:32 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-05-05T17:14:32Z</dc:date>
    <item>
      <title>Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439239#M76586</link>
      <description>&lt;P&gt;Splunk noobie here - basic install on Centos 7, forwarding syslog from security device and the reported date seems to be going backwards, date in syslog message is correct (example below), where should I be looking/checking? &lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/6983i47147BA6069451A3/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 May 2019 12:51:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439239#M76586</guid>
      <dc:creator>johnny21</dc:creator>
      <dc:date>2019-05-05T12:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439240#M76587</link>
      <description>&lt;P&gt;By default, Splunk displays the most recent events first.  That's why dates appear to be going backwards.&lt;/P&gt;

&lt;P&gt;However, you appear to have an odd timestamp format in your events.  To ensure Splunk processes them properly and as a Best Practice, you should add the following to the [syslog] stanza of the appropriate props.conf file&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = &amp;gt;
TIME_FORMAT = %Y:%m%;d-%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 19
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 05 May 2019 17:14:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439240#M76587</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-05-05T17:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439241#M76588</link>
      <description>&lt;P&gt;Also as information this unique syslog is coming from a Sophos UTM security appliance. &lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/6982i4D7537A7BFFD8FCF/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 May 2019 19:44:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439241#M76588</guid>
      <dc:creator>johnny21</dc:creator>
      <dc:date>2019-05-05T19:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439242#M76589</link>
      <description>&lt;P&gt;After making the change when I run splunk btool check --debug I get an error:&lt;/P&gt;

&lt;P&gt;Invalid key in stanza [source::syslog] in /opt/splunk/etc/system/local/inputs.conf, line 4-7&lt;/P&gt;

&lt;P&gt;Is this the correct location where I am supposed to modify props.conf? &lt;BR /&gt;
Is this the correct way to specify a syslog stanza? &lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2019 23:58:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439242#M76589</guid>
      <dc:creator>johnny21</dc:creator>
      <dc:date>2019-05-14T23:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439243#M76590</link>
      <description>&lt;P&gt;Follow up resolution that seems to work - I didn't realize I needed to modify the props.conf file AND the inputs.conf files. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf file&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[splunk@localhost ~]$ cat /opt/splunk/etc/apps/search/local/props.conf
[sophos:syslog]
TIME_PREFIX = &amp;lt;..&amp;gt;
TIME_FORMAT = %Y:%m:%D-%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 19
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;inputs.conf file&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[splunk@localhost ~]$ cat /opt/splunk/etc/apps/search/local/inputs.conf
[tcp://10.0.100.1:5114]
connection_host = ip
source = UTM Syslog
sourcetype = sophos:syslog
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 22 May 2019 13:31:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439243#M76590</guid>
      <dc:creator>johnny21</dc:creator>
      <dc:date>2019-05-22T13:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk date going backwards?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439244#M76591</link>
      <description>&lt;P&gt;If your problem is resolved, please accept an answer to help future readers.&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2019 13:41:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-date-going-backwards/m-p/439244#M76591</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-05-22T13:41:55Z</dc:date>
    </item>
  </channel>
</rss>

