<?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: How to set timezone in an advanced configuration? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10442#M366</link>
    <description>&lt;P&gt;Cross-referencing @Sorkin's &lt;A href="http://splunk-base.splunk.com/answers/11768/timezone-offset"&gt;answer&lt;/A&gt; to a timezone question.&lt;/P&gt;</description>
    <pubDate>Sat, 03 Sep 2011 18:07:47 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2011-09-03T18:07:47Z</dc:date>
    <item>
      <title>How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10432#M356</link>
      <description>&lt;P&gt;If I have a basic input which sets the sourcetype, configuring a timezone offset works great:&lt;/P&gt;

&lt;P&gt;In inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///path/to/foo.log]
sourcetype = foo
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[foo]
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If I have to setup flexible sourcetyping, the above configuration does not work:&lt;/P&gt;

&lt;P&gt;In inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor:///path/to/foo.log]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...foo.log]
TRANSFORMS-abc = setFooSourcetype, setBarSourcetype

[foo]
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm guessing the timezone is set before the new sourcetype is applied so that is why the TZ parameter is not honored.  So I then tried to set the timezone offset using host, which also does not work (no matter the ordering of the stanzas):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::...foo.log]
TRANSFORMS-abc = setFooSourcetype

[host::foohost*]
TZ = GMT
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What other options do I have?  I'm not sure where in the indexing pipeline metadata is set.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Mar 2010 08:51:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10432#M356</guid>
      <dc:creator>hulahoop</dc:creator>
      <dc:date>2010-03-20T08:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10433#M357</link>
      <description>&lt;P&gt;The &lt;CODE&gt;TZ&lt;/CODE&gt; parameter is used and set by the parsing pipeline: &lt;A href="http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F" rel="nofollow"&gt;http://www.splunk.com/wiki/Where_do_I_configure_my_Splunk_settings%3F&lt;/A&gt;
and I believe that timestamp processing occurs before any TRANSFORMS. Setting &lt;CODE&gt;TZ&lt;/CODE&gt; with a &lt;CODE&gt;host::&lt;/CODE&gt; or &lt;CODE&gt;source::&lt;/CODE&gt; stanza should work (as it does with a sourcetype), so I'm not sure why it isn't working for you. Is there another stanza that might also be matching and overriding?&lt;/P&gt;</description>
      <pubDate>Sun, 21 Mar 2010 01:56:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10433#M357</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-03-21T01:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10434#M358</link>
      <description>&lt;P&gt;I think that is precisely the problem--"timestamp processing occurs before any TRANSFORMS."  This data stream requires a sourcetype and host override. Is there a way to re-process TZ &lt;EM&gt;after&lt;/EM&gt; the sourcetype and host override?  Can I create my own processor for this or edit the pipeline order for the parsing queue?&lt;/P&gt;

&lt;P&gt;More details: all events are streamed via TCP by a syslog server, except the events are not in syslog format.  So we need to add index-time rules to assign sourcetype and host.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Mar 2010 09:30:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10434#M358</guid>
      <dc:creator>hulahoop</dc:creator>
      <dc:date>2010-03-22T09:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10435#M359</link>
      <description>&lt;P&gt;oh, okay, yes if you're setting host in props/transforms, then no stanza referring to them is going to work (by that host). Are all events from multiple hosts coming in from that same syslog server? Is it possible to split the hosts from different time zones to different syslog servers &lt;EM&gt;or&lt;/EM&gt; different TCP ports?&lt;/P&gt;</description>
      <pubDate>Mon, 22 Mar 2010 21:24:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10435#M359</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-03-22T21:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10436#M360</link>
      <description>&lt;P&gt;Thank you, G.  We are still in the eval stage here so are reluctant to make changes like this in the production environment.  The preference is to configure Splunk to handle this case if possible.  Are you recommending we do not alter the parsing pipeline?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2010 00:24:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10436#M360</guid>
      <dc:creator>hulahoop</dc:creator>
      <dc:date>2010-03-23T00:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10437#M361</link>
      <description>&lt;P&gt;You really want to declare the TZ by host, ideally, since the logs are almost certainly generated by some system in either its localtime or in GMT.&lt;/P&gt;

&lt;P&gt;However, sometimes life is more complicated than that, like syslog, where the host is identified via a transform, and the original host (used during timestamp extraction) is going to just be where we're acquiring the data.&lt;/P&gt;

&lt;P&gt;In this case you're going to just have to use a source pattern to get reasonable behavior, with the hosts split out into files, for example by syslog-ng.&lt;/P&gt;

&lt;P&gt;Of course if you have the option of simply altering the timestamp format to include the timezone, that's really ideal for ALL parties, not just Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Mar 2010 02:16:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10437#M361</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-03-25T02:16:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10438#M362</link>
      <description>&lt;P&gt;In the current release of Splunk, in the exact scenario described above, it is not possible to apply TZ when using host/sourcetype overriding.  The only alternative is to have the specific hosts forward directly to Splunk so as to create a dedicated source.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Apr 2010 05:31:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10438#M362</guid>
      <dc:creator>hulahoop</dc:creator>
      <dc:date>2010-04-14T05:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10439#M363</link>
      <description>&lt;P&gt;I just ran into this problem.  &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Dec 2010 04:09:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10439#M363</guid>
      <dc:creator>vbumgarner</dc:creator>
      <dc:date>2010-12-22T04:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10440#M364</link>
      <description>&lt;P&gt;Man, it would be nice if Splunk's WinEventLog inputs included timezone information.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Feb 2011 00:51:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10440#M364</guid>
      <dc:creator>gfriedmann</dc:creator>
      <dc:date>2011-02-26T00:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10441#M365</link>
      <description>&lt;P&gt;If the timezone is declared at time of parsing, it is stored.  However, the date parsing code essentially passes the buck for localtime to the system libc, so doesn't know it.  Getting the offset is some work. Getting the timezone is pretty hard.  However, this sounds like work worth doing.  It would be very helpful if you could file an enhancement request with support with one or two use cases to add color to the need.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Mar 2011 02:23:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10441#M365</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2011-03-02T02:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to set timezone in an advanced configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10442#M366</link>
      <description>&lt;P&gt;Cross-referencing @Sorkin's &lt;A href="http://splunk-base.splunk.com/answers/11768/timezone-offset"&gt;answer&lt;/A&gt; to a timezone question.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Sep 2011 18:07:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-set-timezone-in-an-advanced-configuration/m-p/10442#M366</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2011-09-03T18:07:47Z</dc:date>
    </item>
  </channel>
</rss>

