<?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 to prevent scripted input grouping events by time? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-prevent-scripted-input-grouping-events-by-time/m-p/161721#M32798</link>
    <description>&lt;P&gt;That's not how timestamp extraction works. Without knowing your data format, I'd guess this might work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_sourcetype]
TIME_PREFIX = ^([^\t\r\n]*\t){3}
TIME_FORMAT = %Y-%m-%d\t%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 30
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Note, I didn't test if the tab between date and time needs to be a tab character or the baslash-tee of regex.&lt;/P&gt;

&lt;P&gt;The basic Idea is to tell Splunk where to start looking, what to look for, and for how far to keep looking.&lt;BR /&gt;
EXTRACT-foo is search-time field extraction, entirely unrelated to finding the timestamp at index time.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jun 2015 11:51:48 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2015-06-19T11:51:48Z</dc:date>
    <item>
      <title>How to prevent scripted input grouping events by time?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-prevent-scripted-input-grouping-events-by-time/m-p/161720#M32797</link>
      <description>&lt;P&gt;I have a script that executes every 5 minutes. It extracts date and time with props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;EXTRACT-date = ^(?:[^\t\n]*\t){3}(?P&amp;lt;date&amp;gt;[^\t]+)
EXTRACT-time = ^(?:[^\t\n]*\t){4}(?P&amp;lt;time&amp;gt;[^\t]+)
TIMESTAMP_FIELDS = date,time
TIME_FORMAT = %Y-%m-%d %H:%M:%S
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have time field with actually values of event time, but splunk timestamps are grouped by 5 minutes (script execution period). Why is it so, and how I can prevent this behaviour?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2015 10:20:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-prevent-scripted-input-grouping-events-by-time/m-p/161720#M32797</guid>
      <dc:creator>temperuser</dc:creator>
      <dc:date>2015-06-19T10:20:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent scripted input grouping events by time?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-prevent-scripted-input-grouping-events-by-time/m-p/161721#M32798</link>
      <description>&lt;P&gt;That's not how timestamp extraction works. Without knowing your data format, I'd guess this might work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_sourcetype]
TIME_PREFIX = ^([^\t\r\n]*\t){3}
TIME_FORMAT = %Y-%m-%d\t%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 30
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Note, I didn't test if the tab between date and time needs to be a tab character or the baslash-tee of regex.&lt;/P&gt;

&lt;P&gt;The basic Idea is to tell Splunk where to start looking, what to look for, and for how far to keep looking.&lt;BR /&gt;
EXTRACT-foo is search-time field extraction, entirely unrelated to finding the timestamp at index time.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2015 11:51:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-prevent-scripted-input-grouping-events-by-time/m-p/161721#M32798</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2015-06-19T11:51:48Z</dc:date>
    </item>
  </channel>
</rss>

