<?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: How do I configure props.conf to recognize the proper timestamp for my logs? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-configure-props-conf-to-recognize-the-proper-timestamp/m-p/256158#M49188</link>
    <description>&lt;P&gt;Hi daniel333,&lt;/P&gt;

&lt;P&gt;try using &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt; in &lt;CODE&gt;props.conf&lt;/CODE&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = &amp;lt;regular expression&amp;gt;
* If set, splunk scans the event text for a match for this regex in event
  text before attempting to extract a timestamp.
* The timestamping algorithm only looks for a timestamp in the text
  following the end of the first regex match.
* For example, if TIME_PREFIX is set to "abc123", only text following the
  first occurrence of the text abc123 will be used for timestamp extraction.
* If the TIME_PREFIX cannot be found in the event text, timestamp extraction
  will not occur.
* Defaults to empty.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;so, assuming your field looks like this &lt;CODE&gt;start=epoch&lt;/CODE&gt;you can try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
TIME_PREFIX = start=
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But also be aware of the second last line &lt;CODE&gt;If the TIME_PREFIX cannot be found in the event text, timestamp extraction will not occur.&lt;/CODE&gt; So make sure the &lt;CODE&gt;start&lt;/CODE&gt; fields is always available in your events.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Thu, 03 Dec 2015 21:04:16 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-12-03T21:04:16Z</dc:date>
    <item>
      <title>How do I configure props.conf to recognize the proper timestamp for my logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-configure-props-conf-to-recognize-the-proper-timestamp/m-p/256157#M49187</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I have an issue where a small percentage of my logs are coming in dated 2011. I tracked it down to a field called &lt;CODE&gt;usernum=*&lt;/CODE&gt; where some subset of the users account numbers match Epoch time format. So Splunk uses that time as the time. The correct field it should use it &lt;STRONG&gt;start&lt;/STRONG&gt;. &lt;/P&gt;

&lt;P&gt;I assume there is someway to set in the props.conf on the indexers to say&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
Time_Use_Field=start
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But for the life of me the time documentation is going over my head. &lt;/P&gt;</description>
      <pubDate>Thu, 03 Dec 2015 20:23:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-configure-props-conf-to-recognize-the-proper-timestamp/m-p/256157#M49187</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2015-12-03T20:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: How do I configure props.conf to recognize the proper timestamp for my logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-configure-props-conf-to-recognize-the-proper-timestamp/m-p/256158#M49188</link>
      <description>&lt;P&gt;Hi daniel333,&lt;/P&gt;

&lt;P&gt;try using &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt; in &lt;CODE&gt;props.conf&lt;/CODE&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = &amp;lt;regular expression&amp;gt;
* If set, splunk scans the event text for a match for this regex in event
  text before attempting to extract a timestamp.
* The timestamping algorithm only looks for a timestamp in the text
  following the end of the first regex match.
* For example, if TIME_PREFIX is set to "abc123", only text following the
  first occurrence of the text abc123 will be used for timestamp extraction.
* If the TIME_PREFIX cannot be found in the event text, timestamp extraction
  will not occur.
* Defaults to empty.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;so, assuming your field looks like this &lt;CODE&gt;start=epoch&lt;/CODE&gt;you can try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[mysourcetype]
TIME_PREFIX = start=
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But also be aware of the second last line &lt;CODE&gt;If the TIME_PREFIX cannot be found in the event text, timestamp extraction will not occur.&lt;/CODE&gt; So make sure the &lt;CODE&gt;start&lt;/CODE&gt; fields is always available in your events.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 03 Dec 2015 21:04:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-configure-props-conf-to-recognize-the-proper-timestamp/m-p/256158#M49188</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-12-03T21:04:16Z</dc:date>
    </item>
  </channel>
</rss>

