<?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 Overriding TZ for source in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22694#M3522</link>
    <description>&lt;P&gt;I have a JBoss/Tomcat access log that has an incorrect Timezone configuration, causing Splunk to set the time to an hour ahead.&lt;/P&gt;

&lt;P&gt;172.21.138.35 - - [09/Apr/2012:15:51:56.783 -0800] "HEAD /index.html HTTP/1.1" 200 0&lt;/P&gt;

&lt;P&gt;The server is correctly set at PDT, but something is setting this log to stay at -0800.  The developer isn't sure where this is set, and would take some time to correct even when we do find the location.  How do I properly change the time for this source?  It occurs on several hosts (dev/test/staging/production), but only for this source file.&lt;/P&gt;

&lt;P&gt;I've set props.conf on the indexer to:&lt;BR /&gt;
[source::/my/app/path/localhost_access*]&lt;BR /&gt;
TZ=PDT&lt;/P&gt;

&lt;P&gt;Is this incorrect?  It didn't change the behavior and I verified with btool that it's in effect.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Apr 2012 23:00:13 GMT</pubDate>
    <dc:creator>mikelanghorst</dc:creator>
    <dc:date>2012-04-09T23:00:13Z</dc:date>
    <item>
      <title>Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22694#M3522</link>
      <description>&lt;P&gt;I have a JBoss/Tomcat access log that has an incorrect Timezone configuration, causing Splunk to set the time to an hour ahead.&lt;/P&gt;

&lt;P&gt;172.21.138.35 - - [09/Apr/2012:15:51:56.783 -0800] "HEAD /index.html HTTP/1.1" 200 0&lt;/P&gt;

&lt;P&gt;The server is correctly set at PDT, but something is setting this log to stay at -0800.  The developer isn't sure where this is set, and would take some time to correct even when we do find the location.  How do I properly change the time for this source?  It occurs on several hosts (dev/test/staging/production), but only for this source file.&lt;/P&gt;

&lt;P&gt;I've set props.conf on the indexer to:&lt;BR /&gt;
[source::/my/app/path/localhost_access*]&lt;BR /&gt;
TZ=PDT&lt;/P&gt;

&lt;P&gt;Is this incorrect?  It didn't change the behavior and I verified with btool that it's in effect.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 23:00:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22694#M3522</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2012-04-09T23:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22695#M3523</link>
      <description>&lt;P&gt;Splunk uses zoneinfo TZ database values (see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/data/Applytimezoneoffsetstotimestamps"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/data/Applytimezoneoffsetstotimestamps&lt;/A&gt; and &lt;A href="http://en.wikipedia.org/wiki/List_of_zoneinfo_timezones"&gt;http://en.wikipedia.org/wiki/List_of_zoneinfo_timezones&lt;/A&gt; ). Did you try US/Pacific for the TZ value?&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 23:26:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22695#M3523</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2012-04-09T23:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22696#M3524</link>
      <description>&lt;P&gt;Yes, I just tried TZ=US/Pacific, but no change.&lt;/P&gt;

&lt;P&gt;»  4/9/12&lt;BR /&gt;
5:29:41.000 PM  &lt;/P&gt;

&lt;P&gt;[09/Apr/2012:16:29:41 -0800] 172.27.140.119 user1 - HTTP/1.1 POST 200 8969 98 /app/unitSubstitution/loadJSON&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 23:31:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22696#M3524</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2012-04-09T23:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22697#M3525</link>
      <description>&lt;P&gt;Some additional things worth trying:&lt;/P&gt;

&lt;P&gt;First, set an explicit &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; and &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; in addition to a &lt;CODE&gt;TZ&lt;/CODE&gt; for this source.  Make the &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; and &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; explicitly ignore the "-0800" bit, preferably by setting &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; small enough to where the "-0800" part isn't considered.&lt;/P&gt;

&lt;P&gt;If that doesn't work, as hideous as it is you could filter out the "-0800" using a SEDCMD.  (I really hope it doesn't come to this)&lt;/P&gt;</description>
      <pubDate>Tue, 10 Apr 2012 00:27:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22697#M3525</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-04-10T00:27:04Z</dc:date>
    </item>
    <item>
      <title>Re: Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22698#M3526</link>
      <description>&lt;P&gt;Used the data import function on my local instance to set this up.  Looks like this will be the answer.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Apr 2012 15:22:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22698#M3526</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2012-04-10T15:22:56Z</dc:date>
    </item>
    <item>
      <title>Re: Overriding TZ for source</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22699#M3527</link>
      <description>&lt;P&gt;You should be able to use &lt;CODE&gt;TZ_ALIAS&lt;/CODE&gt; like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TZ_ALIAS=-0800=PDT
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 29 Jun 2015 03:48:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Overriding-TZ-for-source/m-p/22699#M3527</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-06-29T03:48:36Z</dc:date>
    </item>
  </channel>
</rss>

