<?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 What timezone does collect use? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-timezone-does-collect-use/m-p/422843#M74255</link>
    <description>&lt;P&gt;There is something wrong (or not obvious from the documentation) with how &lt;CODE&gt;collect&lt;/CODE&gt; takes timezones.&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;_time&lt;/CODE&gt; fields should be stored in unixtime, right?&lt;/P&gt;
&lt;P&gt;I have a report which does a long search and I use &lt;CODE&gt;collect&lt;/CODE&gt; to take a &lt;CODE&gt;_time&lt;/CODE&gt; and I use &lt;CODE&gt;addtime=t&lt;/CODE&gt; to use that &lt;CODE&gt;_time&lt;/CODE&gt; in the new field.&lt;/P&gt;
&lt;P&gt;The original timestamp is stored as:&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;2019-07-29 23:16:51.884 INFO ...&lt;/CODE&gt; in &lt;CODE&gt;_raw&lt;/CODE&gt; (UTC). And its &lt;CODE&gt;timestamp&lt;/CODE&gt; field is set to &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; (UTC) and in my browser, the &lt;CODE&gt;_time&lt;/CODE&gt; is set as &lt;CODE&gt;2019-07-29T16:16:51.884-07:00&lt;/CODE&gt;. That's all correct.&lt;/P&gt;
&lt;P&gt;When I use &lt;CODE&gt;collect&lt;/CODE&gt; and use that &lt;CODE&gt;_time&lt;/CODE&gt;, it gets stored as &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; in the &lt;CODE&gt;_raw&lt;/CODE&gt;, &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; in the &lt;CODE&gt;timestamp&lt;/CODE&gt; field, but it incorrectly uses &lt;CODE&gt;2019-07-29T23:16:51.884-07:00&lt;/CODE&gt; for &lt;CODE&gt;_time&lt;/CODE&gt;. I don't know why it's using that timezone when it's passing the &lt;CODE&gt;_time&lt;/CODE&gt; (which I thought was unixtime, which is always UTC).&lt;/P&gt;
&lt;P&gt;How can I correct for this bug in Splunk?&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jun 2020 00:01:06 GMT</pubDate>
    <dc:creator>khevans</dc:creator>
    <dc:date>2020-06-07T00:01:06Z</dc:date>
    <item>
      <title>What timezone does collect use?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-timezone-does-collect-use/m-p/422843#M74255</link>
      <description>&lt;P&gt;There is something wrong (or not obvious from the documentation) with how &lt;CODE&gt;collect&lt;/CODE&gt; takes timezones.&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;_time&lt;/CODE&gt; fields should be stored in unixtime, right?&lt;/P&gt;
&lt;P&gt;I have a report which does a long search and I use &lt;CODE&gt;collect&lt;/CODE&gt; to take a &lt;CODE&gt;_time&lt;/CODE&gt; and I use &lt;CODE&gt;addtime=t&lt;/CODE&gt; to use that &lt;CODE&gt;_time&lt;/CODE&gt; in the new field.&lt;/P&gt;
&lt;P&gt;The original timestamp is stored as:&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;2019-07-29 23:16:51.884 INFO ...&lt;/CODE&gt; in &lt;CODE&gt;_raw&lt;/CODE&gt; (UTC). And its &lt;CODE&gt;timestamp&lt;/CODE&gt; field is set to &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; (UTC) and in my browser, the &lt;CODE&gt;_time&lt;/CODE&gt; is set as &lt;CODE&gt;2019-07-29T16:16:51.884-07:00&lt;/CODE&gt;. That's all correct.&lt;/P&gt;
&lt;P&gt;When I use &lt;CODE&gt;collect&lt;/CODE&gt; and use that &lt;CODE&gt;_time&lt;/CODE&gt;, it gets stored as &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; in the &lt;CODE&gt;_raw&lt;/CODE&gt;, &lt;CODE&gt;2019-07-29 23:16:51.884&lt;/CODE&gt; in the &lt;CODE&gt;timestamp&lt;/CODE&gt; field, but it incorrectly uses &lt;CODE&gt;2019-07-29T23:16:51.884-07:00&lt;/CODE&gt; for &lt;CODE&gt;_time&lt;/CODE&gt;. I don't know why it's using that timezone when it's passing the &lt;CODE&gt;_time&lt;/CODE&gt; (which I thought was unixtime, which is always UTC).&lt;/P&gt;
&lt;P&gt;How can I correct for this bug in Splunk?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 00:01:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-timezone-does-collect-use/m-p/422843#M74255</guid>
      <dc:creator>khevans</dc:creator>
      <dc:date>2020-06-07T00:01:06Z</dc:date>
    </item>
    <item>
      <title>Re: What timezone does collect use?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-timezone-does-collect-use/m-p/422844#M74256</link>
      <description>&lt;P&gt;Seeing this exact same thing. Somehow my timestamp (_time) has -07:00 on the end of it, and this is not the timezone setting of my laptop, or the dataset (in a different timezone). Very strange indeed. Cannot find any other comments about this other than your post.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 15:35:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-timezone-does-collect-use/m-p/422844#M74256</guid>
      <dc:creator>joesrepsolc</dc:creator>
      <dc:date>2020-06-03T15:35:07Z</dc:date>
    </item>
  </channel>
</rss>

