<?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: what do the indexed fields `timeendpos` and `timestartpos` represent? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/what-do-the-indexed-fields-timeendpos-and-timestartpos-represent/m-p/99961#M20876</link>
    <description>&lt;P&gt;They mean just how far into the event that Splunk thinks (usually correct) that your timestamp goes.&lt;/P&gt;

&lt;P&gt;timestartpos (at which byte the timestamp starts)&lt;BR /&gt;
timeendpos (at which bye into the event the timestamp ends)&lt;/P&gt;

&lt;P&gt;If you are experiencing timestamping issues, you should look into how you can alter this behaviour through props.conf settings for your sourcetype;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIMESTAMP_LOOKAHEAD = number
TIME_FORMAT = strftime format
TIME_PREFIX = regex
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
    <pubDate>Fri, 23 Mar 2012 01:47:22 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2012-03-23T01:47:22Z</dc:date>
    <item>
      <title>what do the indexed fields `timeendpos` and `timestartpos` represent?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/what-do-the-indexed-fields-timeendpos-and-timestartpos-represent/m-p/99960#M20875</link>
      <description>&lt;P&gt;I am new to Splunk.&lt;/P&gt;

&lt;P&gt;What do the indexed fields &lt;CODE&gt;timeendpos&lt;/CODE&gt; and &lt;CODE&gt;timestartpos&lt;/CODE&gt; represent?&lt;/P&gt;

&lt;P&gt;Since one report the company asks for from our archived Apache log files is the duration of the longest queries, I am curious about these fields and how to translate the corresponding integer values, if they have meaning.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2012 00:50:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/what-do-the-indexed-fields-timeendpos-and-timestartpos-represent/m-p/99960#M20875</guid>
      <dc:creator>boris</dc:creator>
      <dc:date>2012-03-23T00:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: what do the indexed fields `timeendpos` and `timestartpos` represent?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/what-do-the-indexed-fields-timeendpos-and-timestartpos-represent/m-p/99961#M20876</link>
      <description>&lt;P&gt;They mean just how far into the event that Splunk thinks (usually correct) that your timestamp goes.&lt;/P&gt;

&lt;P&gt;timestartpos (at which byte the timestamp starts)&lt;BR /&gt;
timeendpos (at which bye into the event the timestamp ends)&lt;/P&gt;

&lt;P&gt;If you are experiencing timestamping issues, you should look into how you can alter this behaviour through props.conf settings for your sourcetype;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIMESTAMP_LOOKAHEAD = number
TIME_FORMAT = strftime format
TIME_PREFIX = regex
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2012 01:47:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/what-do-the-indexed-fields-timeendpos-and-timestartpos-represent/m-p/99961#M20876</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-03-23T01:47:22Z</dc:date>
    </item>
  </channel>
</rss>

