<?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: timestamp recognition on a split date and time with no prefix in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323039#M60152</link>
    <description>&lt;P&gt;This is all (original file, sa-eventgen, conf files etc) on a single instance. The extractions don't happen on the streaming events from the eventgen like they do on the file input and that seems to be the root of the issue - even though I'm using the same sourcetype and event format (minus the header row that was in the original csv file). I'm stumped!&lt;/P&gt;

&lt;P&gt;I'm wondering if indexed field extractions occur after timestamping on streaming data for some reason, which was why I was headed down the path of treating the events as raw data and using time_format or datetime.xml. Any other thoughts let me know and thanks so much for the help!&lt;/P&gt;</description>
    <pubDate>Sat, 22 Jul 2017 18:55:51 GMT</pubDate>
    <dc:creator>bgilmore_splunk</dc:creator>
    <dc:date>2017-07-22T18:55:51Z</dc:date>
    <item>
      <title>timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323035#M60148</link>
      <description>&lt;P&gt;I have events that start with a format similar to:&lt;/P&gt;

&lt;P&gt;14-Jul-17,7:23:00 PM,7:23:36 PM,7:23:36 PM,-36,206&lt;/P&gt;

&lt;P&gt;where the first field is the date and the fourth field is the time - the middle two time fields are always different - makes me wish you could use regex in time_format. Hoping to avoid datetime.xml, but maybe I'm missing something simple here? Appreciate any ideas!&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 02:54:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323035#M60148</guid>
      <dc:creator>bgilmore_splunk</dc:creator>
      <dc:date>2017-07-22T02:54:48Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323036#M60149</link>
      <description>&lt;P&gt;indexed_extractions=csv makes pretty easy work of it with:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[ csv_timestampfu ]
CHARSET=UTF-8
INDEXED_EXTRACTIONS=csv
KV_MODE=none
SHOULD_LINEMERGE=false
category=Custom
description=Comma-separated value format, using TIMESTAMP_FIELDS to craft _time
disabled=false
pulldown_type=true
FIELD_NAMES=1,2,3,4,5,6 # set your schema
TIME_FORMAT=%d-%b-%y %I:%M:%S
TIMESTAMP_FIELDS=1,4 # parse from field 1 &amp;amp; 4 as per time_format
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;IMG src="http://i.imgur.com/FTob92s.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;Could probably eval at search time as well if necessary. &lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 04:51:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323036#M60149</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-07-22T04:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323037#M60150</link>
      <description>&lt;P&gt;Thats what I thought too, its how I was originally approaching, but couldn't get it to work so I was looking for another route. Here's my current props:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[telemetry1]
CHARSET=UTF-8
INDEXED_EXTRACTIONS = csv
KV_MODE = none
SHOULD_LINEMERGE = false
pulldown_type = true
category = Custom
FIELD_NAMES = calendar_day, scheduled_time, actual_arrival_time, actual_depart_time, adherence_seconds, time_point_id
TIMESTAMP_FIELDS = calendar_day, actual_depart_time
TIME_FORMAT = %d-%b-%y %I:%M:%S %p
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But ts recognition is failing and Splunk is just using index time. SA-eventgen is the datasource if that makes a difference, events are coming in over STDOUT. I'll keep poking, but any other thoughts are appreciated - thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 18:24:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323037#M60150</guid>
      <dc:creator>bgilmore_splunk</dc:creator>
      <dc:date>2017-07-22T18:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323038#M60151</link>
      <description>&lt;P&gt;hmm are the csv extractions happening? Any chance you are using a UF and didn't put the props there?&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 18:44:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323038#M60151</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-07-22T18:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323039#M60152</link>
      <description>&lt;P&gt;This is all (original file, sa-eventgen, conf files etc) on a single instance. The extractions don't happen on the streaming events from the eventgen like they do on the file input and that seems to be the root of the issue - even though I'm using the same sourcetype and event format (minus the header row that was in the original csv file). I'm stumped!&lt;/P&gt;

&lt;P&gt;I'm wondering if indexed field extractions occur after timestamping on streaming data for some reason, which was why I was headed down the path of treating the events as raw data and using time_format or datetime.xml. Any other thoughts let me know and thanks so much for the help!&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 18:55:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323039#M60152</guid>
      <dc:creator>bgilmore_splunk</dc:creator>
      <dc:date>2017-07-22T18:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp recognition on a split date and time with no prefix</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323040#M60153</link>
      <description>&lt;P&gt;Here's my full btool dump for the sourcetype if it helps:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[telemetry1]
ANNOTATE_PUNCT = True
AUTO_KV_JSON = true
BREAK_ONLY_BEFORE = 
BREAK_ONLY_BEFORE_DATE = True
CHARSET = UTF-8
DATETIME_CONFIG = 
EVAL-lat = substr(latitude, 1, 2).".".substr(latitude, 3, 7)
EVAL-lon = substr(longitude, 1, 3).".".substr(longitude, 4, 7)
FIELD_NAMES = calendar_day, scheduled_time, actual_arrival_time, actual_depart_time, adherence_seconds, time_point_id, time_point_name, block_stop_order, vehicle_num, geo_node, latitude, longitude, schd_distance, route_abbr, is_layover, route_name, isrevenue, revenue_id
HEADER_MODE = 
INDEXED_EXTRACTIONS = csv
KV_MODE = none
LEARN_MODEL = true
LEARN_SOURCETYPE = true
LINE_BREAKER_LOOKBEHIND = 100
MATCH_LIMIT = 100000
MAX_DAYS_AGO = 2000
MAX_DAYS_HENCE = 2
MAX_DIFF_SECS_AGO = 3600
MAX_DIFF_SECS_HENCE = 604800
MAX_EVENTS = 256
MAX_TIMESTAMP_LOOKAHEAD = 128
MUST_BREAK_AFTER = 
MUST_NOT_BREAK_AFTER = 
MUST_NOT_BREAK_BEFORE = 
NO_BINARY_CHECK = true
SEGMENTATION = indexing
SEGMENTATION-all = full
SEGMENTATION-inner = inner
SEGMENTATION-outer = outer
SEGMENTATION-raw = none
SEGMENTATION-standard = standard
SHOULD_LINEMERGE = false
TIMESTAMP_FIELDS = calendar_day, actual_depart_time
TIME_FORMAT = %d-%b-%y %I:%M:%S %p
TRANSFORMS = 
TRUNCATE = 10000
category = Structured
description = MARTA AVL Import
detect_trailing_nulls = false
disabled = false
maxDist = 100
priority = 
pulldown_type = true
sourcetype = 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 22 Jul 2017 19:22:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-recognition-on-a-split-date-and-time-with-no-prefix/m-p/323040#M60153</guid>
      <dc:creator>bgilmore_splunk</dc:creator>
      <dc:date>2017-07-22T19:22:36Z</dc:date>
    </item>
  </channel>
</rss>

