<?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 Summary indexes and multiple time zones in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Summary-indexes-and-multiple-time-zones/m-p/131154#M26958</link>
    <description>&lt;P&gt;In an environment that provides reporting across many different time zones, should summary searches run under a user set to the default system time, GMT time, or doesn't it matter since Splunk will adjust the time based on the user's time zone?&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2015 14:14:21 GMT</pubDate>
    <dc:creator>sc0tt</dc:creator>
    <dc:date>2015-04-08T14:14:21Z</dc:date>
    <item>
      <title>Summary indexes and multiple time zones</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Summary-indexes-and-multiple-time-zones/m-p/131154#M26958</link>
      <description>&lt;P&gt;In an environment that provides reporting across many different time zones, should summary searches run under a user set to the default system time, GMT time, or doesn't it matter since Splunk will adjust the time based on the user's time zone?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2015 14:14:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Summary-indexes-and-multiple-time-zones/m-p/131154#M26958</guid>
      <dc:creator>sc0tt</dc:creator>
      <dc:date>2015-04-08T14:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Summary indexes and multiple time zones</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Summary-indexes-and-multiple-time-zones/m-p/131155#M26959</link>
      <description>&lt;P&gt;Generally, it doesn't matter because the &lt;CODE&gt;_time&lt;/CODE&gt; field that is created for the events in the summary index is always normalized to GMT epoch.  There is one thing to consider, though; if you are using any &lt;CODE&gt;snap-to&lt;/CODE&gt; definitions, these may be effected by the user's &lt;CODE&gt;Time zone&lt;/CODE&gt; value.  For example, if your TZ offset is not an even-hour (I just read that North Korea is dropping 30 minutes from their TZ), then &lt;CODE&gt;@h&lt;/CODE&gt; for one user may be 30 minutes different than &lt;CODE&gt;@h&lt;/CODE&gt; for another user.  The same concern exists for relative &lt;EM&gt;day&lt;/EM&gt; specifiers anywhere they exist (not just for the &lt;CODE&gt;snap-to&lt;/CODE&gt; part) because where midnight falls (e.g. where the DayChange time is), may be different for different users so the window for &lt;CODE&gt;day&lt;/CODE&gt; can be different from user-to-user.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2015 20:55:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Summary-indexes-and-multiple-time-zones/m-p/131155#M26959</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-08-09T20:55:06Z</dc:date>
    </item>
  </channel>
</rss>

