<?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: Should Splunk be barking back at this type of time stamp string? 2016/04/07T10:04:02.113[+0000] ? I can't tell if it meets the ISO standard. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285700#M54579</link>
    <description>&lt;P&gt;Thanks Rich !! I am glad I was onto something. I appreciate your very quick response !!&lt;/P&gt;</description>
    <pubDate>Thu, 07 Apr 2016 14:38:22 GMT</pubDate>
    <dc:creator>dmacgillivray</dc:creator>
    <dc:date>2016-04-07T14:38:22Z</dc:date>
    <item>
      <title>Should Splunk be barking back at this type of time stamp string? 2016/04/07T10:04:02.113[+0000] ? I can't tell if it meets the ISO standard.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285698#M54577</link>
      <description>&lt;P&gt;Hello Splunkers,&lt;/P&gt;

&lt;P&gt;I have a timestamp below that does not seem to want to get recognized / converted properly by Splunk.&lt;/P&gt;

&lt;P&gt;Do I need to have the developers in house adjust their feed? I am assuming this may not be a standard ISO stamp below? I thought it was, but it will not allow us to properly search data within Splunk.&lt;/P&gt;

&lt;P&gt;The "Event" stamp below came from GMT and showed up as GMT in the "Time" column and is not converting to EST like we would expect our default login settings and indexers are set to.&lt;/P&gt;

&lt;P&gt;Here is the stamp below. Thanks in advance for any help you may be able to provide.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2016/04/07T10:04:02.113[+0000]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 07 Apr 2016 14:16:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285698#M54577</guid>
      <dc:creator>dmacgillivray</dc:creator>
      <dc:date>2016-04-07T14:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Should Splunk be barking back at this type of time stamp string? 2016/04/07T10:04:02.113[+0000] ? I can't tell if it meets the ISO standard.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285699#M54578</link>
      <description>&lt;P&gt;Go back to your developers.  ISO 8601 timestamps, which it appears you're trying to use, are in the format YYYY-mm-ddTHH:MM:SS.sss+HHMM.&lt;BR /&gt;
Note the use of dashes rather than slashes in the date portion.  The time offset should not be enclosed in brackets.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 14:35:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285699#M54578</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2016-04-07T14:35:48Z</dc:date>
    </item>
    <item>
      <title>Re: Should Splunk be barking back at this type of time stamp string? 2016/04/07T10:04:02.113[+0000] ? I can't tell if it meets the ISO standard.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285700#M54579</link>
      <description>&lt;P&gt;Thanks Rich !! I am glad I was onto something. I appreciate your very quick response !!&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 14:38:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Should-Splunk-be-barking-back-at-this-type-of-time-stamp-string/m-p/285700#M54579</guid>
      <dc:creator>dmacgillivray</dc:creator>
      <dc:date>2016-04-07T14:38:22Z</dc:date>
    </item>
  </channel>
</rss>

