<?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 Timestamp in props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131762#M27102</link>
    <description>&lt;P&gt;My event looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Jan 30 10:32:43 192.168.1.1 Netdefender: 30-01-2014 02:54:05 WARNING
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We would like to use the second timestamp for our events. We have configured props.conf in /local like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[netdefender]
TIME_PREFIX = \w+\s\d+\s\d{2}:\d{2}:\d{2}\s\d+\.\d+\.\d+\.\d+\s\w+\:\s
MAX_TIMESTAMP_LOOKAHEAD = 44
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We are still seeing index time as the timestamp. What are we missing?&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2014 16:02:38 GMT</pubDate>
    <dc:creator>splunkingsplun1</dc:creator>
    <dc:date>2014-01-30T16:02:38Z</dc:date>
    <item>
      <title>Timestamp in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131762#M27102</link>
      <description>&lt;P&gt;My event looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Jan 30 10:32:43 192.168.1.1 Netdefender: 30-01-2014 02:54:05 WARNING
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We would like to use the second timestamp for our events. We have configured props.conf in /local like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[netdefender]
TIME_PREFIX = \w+\s\d+\s\d{2}:\d{2}:\d{2}\s\d+\.\d+\.\d+\.\d+\s\w+\:\s
MAX_TIMESTAMP_LOOKAHEAD = 44
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We are still seeing index time as the timestamp. What are we missing?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 16:02:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131762#M27102</guid>
      <dc:creator>splunkingsplun1</dc:creator>
      <dc:date>2014-01-30T16:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131763#M27103</link>
      <description>&lt;P&gt;The config below should work.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[netdefender]
TIME_PREFIX = :\s
TIME_FORMAT = %d-%m-%Y %H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Further things to check:&lt;/P&gt;

&lt;P&gt;You have edited &lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings"&gt;the correct props.conf file&lt;/A&gt;? &lt;/P&gt;

&lt;P&gt;The sourcetype name is correct?&lt;/P&gt;

&lt;P&gt;You are aware that this only affects new events coming in?&lt;/P&gt;

&lt;P&gt;You have restarted Splunk?&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 16:12:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131763#M27103</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-01-30T16:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp in props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131764#M27104</link>
      <description>&lt;P&gt;Thank you that did what we needed!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 19:46:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timestamp-in-props-conf/m-p/131764#M27104</guid>
      <dc:creator>splunkingsplun1</dc:creator>
      <dc:date>2014-01-30T19:46:54Z</dc:date>
    </item>
  </channel>
</rss>

