<?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: Timezone Offset in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46104#M8680</link>
    <description>&lt;P&gt;Yes. I believe this is a shortcoming of splunk at the moment. I have run into this problem with windows light forwarders, but i don't even have a hostname convention method to help deal with local timezone settings. We run servers that must be configured in the audience's timezone.&lt;/P&gt;</description>
    <pubDate>Sat, 26 Feb 2011 00:58:23 GMT</pubDate>
    <dc:creator>gfriedmann</dc:creator>
    <dc:date>2011-02-26T00:58:23Z</dc:date>
    <item>
      <title>Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46101#M8677</link>
      <description>&lt;P&gt;Can this configuration be made on the forwarder, or must it be placed on the indexer?&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::nyc*] 
TZ = US/Eastern
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 17 Feb 2011 06:49:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46101#M8677</guid>
      <dc:creator>carmackd</dc:creator>
      <dc:date>2011-02-17T06:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46102#M8678</link>
      <description>&lt;P&gt;It must be placed on the server that's parsing the data. If it's a heavyweight forwarder, it goes on the forwarder. If it's a light forwarder, it goes on the indexer.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2011 06:53:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46102#M8678</guid>
      <dc:creator>Stephen_Sorkin</dc:creator>
      <dc:date>2011-02-17T06:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46103#M8679</link>
      <description>&lt;P&gt;So, if we have a mix of 1000s of heavy and lightweight forwarders, we cant just stick the TZ for each host in the props.conf on the indexers? &lt;/P&gt;

&lt;P&gt;We have to identify the heavy forwarders and ensure they have this set in their local props.conf on each heavy forwarder (an arduous task in our environment)?&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2011 02:20:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46103#M8679</guid>
      <dc:creator>pj</dc:creator>
      <dc:date>2011-02-18T02:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46104#M8680</link>
      <description>&lt;P&gt;Yes. I believe this is a shortcoming of splunk at the moment. I have run into this problem with windows light forwarders, but i don't even have a hostname convention method to help deal with local timezone settings. We run servers that must be configured in the audience's timezone.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Feb 2011 00:58:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46104#M8680</guid>
      <dc:creator>gfriedmann</dc:creator>
      <dc:date>2011-02-26T00:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46105#M8681</link>
      <description>&lt;P&gt;I am using Splunk Universal Forwarder 4.3.2 on Windows sending IIS logs to a Splunk 4.3.2 server on CentOS. I had to add the timezone to /opt/splunk/etc/system/local/props.conf on the server:&lt;/P&gt;

&lt;P&gt;[iis]&lt;BR /&gt;
TZ = GMT&lt;/P&gt;

&lt;P&gt;[iis-1]&lt;BR /&gt;
TZ = GMT&lt;/P&gt;

&lt;P&gt;The events ended up having sourcetype [iis-1] on the server because of CHECK_FOR_HEADER being enabled on the forwarder (&lt;A href="http://splunk-base.splunk.com/answers/72860/sourcetypes-keep-on-multiplying/72883" target="_blank"&gt;http://splunk-base.splunk.com/answers/72860/sourcetypes-keep-on-multiplying/72883&lt;/A&gt;), hence the two stanzas.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:43:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46105#M8681</guid>
      <dc:creator>clabu</dc:creator>
      <dc:date>2020-09-28T14:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Timezone Offset</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46106#M8682</link>
      <description>&lt;P&gt;Starting in Splunk 6, it's now possible to specify the timezone on a Universal Forwarder.  As long as both sender and receiver are using the new forwarding protocol, the timezone information provided by the sender should be honored.&lt;/P&gt;

&lt;P&gt;Links to related docs:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/data/Applytimezoneoffsetstotimestamps"&gt;Specify time zones of timestamps&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf"&gt;props.conf&lt;/A&gt; - Look at the "&lt;CODE&gt;TZ&lt;/CODE&gt;" attribute.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.3/Admin/Outputsconf"&gt;outputs.conf&lt;/A&gt;.  The new protocol can be enabled/disabled with &lt;CODE&gt;negotiateNewProtocol&lt;/CODE&gt;.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 17 Apr 2014 17:39:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Timezone-Offset/m-p/46106#M8682</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2014-04-17T17:39:18Z</dc:date>
    </item>
  </channel>
</rss>

