<?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 question in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114085#M23849</link>
    <description>&lt;P&gt;Try setting &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD = 20&lt;/CODE&gt; in your props.conf.  That will keep Splunk from trying to interpret 1.2.3.4 as the TZ.&lt;/P&gt;</description>
    <pubDate>Wed, 15 Jan 2014 02:51:02 GMT</pubDate>
    <dc:creator>lukejadamec</dc:creator>
    <dc:date>2014-01-15T02:51:02Z</dc:date>
    <item>
      <title>timezone question</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114083#M23847</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a feed that sends messages using the UTC timezone.  The timezone itself is never listed, but the vendor has assured me that this is the case (and it looks correct).  Should I reference the timezone with a "TZ = UTC" in props.conf, or should I put a %T in the TIME_FORMAT, even though the timezone isn't in the message.  &lt;/P&gt;

&lt;P&gt;For example:&lt;/P&gt;

&lt;P&gt;2014-01-14 23:54:17 1.2.3.4 message....&lt;/P&gt;

&lt;P&gt;My props.conf has:&lt;/P&gt;

&lt;P&gt;TIME_FORMAT = %Y-%m-%d %H:%M:%S&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TIME_PREFIX = ^&lt;BR /&gt;
TZ = UTC&lt;/P&gt;

&lt;P&gt;or should it have:&lt;BR /&gt;
TIME_FORMAT = %Y-%m-%d %H:%M:%S %T&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
TIME_PREFIX = ^&lt;/P&gt;

&lt;P&gt;Update: it appears to be ignoring my timezone, regardless.  As the event times are matching what is in the logs, and that should not be the case.  &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:39:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114083#M23847</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2020-09-28T15:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: timezone question</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114084#M23848</link>
      <description>&lt;P&gt;What is your user default timezone?  Splunk will adjust the search results based on the user timezone.&lt;BR /&gt;
If no timezone is available in the event, then Splunk uses the indexer timezone.  What is the indexer timezone?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2014 02:45:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114084#M23848</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-01-15T02:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: timezone question</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114085#M23849</link>
      <description>&lt;P&gt;Try setting &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD = 20&lt;/CODE&gt; in your props.conf.  That will keep Splunk from trying to interpret 1.2.3.4 as the TZ.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2014 02:51:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timezone-question/m-p/114085#M23849</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-01-15T02:51:02Z</dc:date>
    </item>
  </channel>
</rss>

