<?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: Source type Timestamp settings. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446850#M77741</link>
    <description>&lt;P&gt;Hello @spilepich,&lt;BR /&gt;
Well, I think you get both. In _time, you get the value extracted from message.date, which enable to display it according to the user timezone, as configured in Splunk. In message.date, you get the value contained in the original json event.&lt;/P&gt;

&lt;P&gt;This is the standard behaviour in Splunk&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jul 2018 06:53:53 GMT</pubDate>
    <dc:creator>poete</dc:creator>
    <dc:date>2018-07-19T06:53:53Z</dc:date>
    <item>
      <title>Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446846#M77737</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm trying to set up a source type that parses the date from an inner field (message.date in the below example) however the &lt;CODE&gt;_time&lt;/CODE&gt; value is always set as the processed time. Any guesses as to what i might be doing wrong?&lt;/P&gt;

&lt;P&gt;The configuration is as follows:&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/5383i45787AD9C0AF3CF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;This is a sample event.&lt;BR /&gt;
  &lt;CODE&gt;&lt;BR /&gt;
{"message":{"_id":"some_value","date":"2018-07-18T04:40:58.071Z","type":"fsa","description":"Login required","client_id":"some_value","client_name":"some_value","ip":"some_value","user_agent":"Chrome 67.0.3396 / Windows 10 0.0.0","details":{"body":{"tenant":"some_value"},"qs":{"client_id":"some_value","response_type":"id_token","response_mode":"web_message","redirect_uri":"some_value","scope":"openid email profile","audience":"some_value","leeway":"60","state":"some_value","nonce":"some_value","prompt":"none","auth0Client":"some_value","tenant":"hirer"},"connection":null,"error":{"message":"Login required","oauthError":"login_required","type":"oauth-authorization"}},"hostname":"a","session_connection":null,"session_connection_id":null,"audience":"o","scope":["openid","email","profile"],"isMobile":false},"severity":"info"}&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 06:07:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446846#M77737</guid>
      <dc:creator>spilepich</dc:creator>
      <dc:date>2018-07-18T06:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446847#M77738</link>
      <description>&lt;P&gt;Hello @spilepich,&lt;/P&gt;

&lt;P&gt;why bother with configuring the extraction? I did import the sample of data successfuly using the &lt;STRONG&gt;Auto&lt;/STRONG&gt; Extraction.&lt;/P&gt;

&lt;P&gt;But maybe you are trying to do something I did not get. Did, you try with &lt;STRONG&gt;Auto&lt;/STRONG&gt;?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 14:28:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446847#M77738</guid>
      <dc:creator>poete</dc:creator>
      <dc:date>2018-07-18T14:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446848#M77739</link>
      <description>&lt;P&gt;i would try what @poete is suggesting instead of changing it to _json leave it as default and then add your timestamp format in. I tested it with your sample event and it works great. &lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 15:21:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446848#M77739</guid>
      <dc:creator>CarsonZa</dc:creator>
      <dc:date>2018-07-18T15:21:06Z</dc:date>
    </item>
    <item>
      <title>Re: Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446849#M77740</link>
      <description>&lt;P&gt;yes, that's the first thing i tried. The data imports with the load time as &lt;CODE&gt;_time&lt;/CODE&gt; instead of what is in &lt;CODE&gt;message.date&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 06:26:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446849#M77740</guid>
      <dc:creator>spilepich</dc:creator>
      <dc:date>2018-07-19T06:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446850#M77741</link>
      <description>&lt;P&gt;Hello @spilepich,&lt;BR /&gt;
Well, I think you get both. In _time, you get the value extracted from message.date, which enable to display it according to the user timezone, as configured in Splunk. In message.date, you get the value contained in the original json event.&lt;/P&gt;

&lt;P&gt;This is the standard behaviour in Splunk&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 06:53:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446850#M77741</guid>
      <dc:creator>poete</dc:creator>
      <dc:date>2018-07-19T06:53:53Z</dc:date>
    </item>
    <item>
      <title>Re: Source type Timestamp settings.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446851#M77742</link>
      <description>&lt;P&gt;This was a HEC input going to the standard endpoint, which expects data to be formatted a certain way:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Event_metadata"&gt;http://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Event_metadata&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It will not extract timestamps from JSON fields other than "time" in epoch format.&lt;BR /&gt;
To resolve, use the raw endpoint, which will do default field extraction as per sourcetype configuration:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Raw_event_parsing"&gt;http://docs.splunk.com/Documentation/Splunk/7.1.2/Data/FormateventsforHTTPEventCollector#Raw_event_parsing&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope that helps!&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 03:07:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-type-Timestamp-settings/m-p/446851#M77742</guid>
      <dc:creator>eavent_splunk</dc:creator>
      <dc:date>2018-09-04T03:07:42Z</dc:date>
    </item>
  </channel>
</rss>

