<?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: Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp;amp; hosts scattered around th in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544609#M4899</link>
    <description>&lt;P&gt;Splunk converts timestamps into a common time zone when they are received and the converts them to the user's preferred time zone at display time.&amp;nbsp; If a timestamp is in the wrong zone then it probably was ingested incorrectly.&lt;/P&gt;&lt;P&gt;Ideally, the timestamp of an event will contain zone information.&amp;nbsp; Failing that, the forwarder which sent the event can use the &lt;FONT face="courier new,courier"&gt;TZ&lt;/FONT&gt; setting in props.conf to specify the correct time zone.&lt;/P&gt;&lt;P&gt;Tell us more about the use case and we may be able to offer other solutions.&lt;/P&gt;</description>
    <pubDate>Sat, 20 Mar 2021 12:23:13 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2021-03-20T12:23:13Z</dc:date>
    <item>
      <title>Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp; hosts scattered around the US?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544563#M4895</link>
      <description>&lt;P&gt;Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp;amp; hosts scattered around the US?&lt;/P&gt;&lt;P&gt;How does one prepare a report of the Hosts having time zone differences &amp;amp; ways to fix the issues.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Mar 2021 19:04:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544563#M4895</guid>
      <dc:creator>SamHTexas</dc:creator>
      <dc:date>2021-03-19T19:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp; hosts scattered around th</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544609#M4899</link>
      <description>&lt;P&gt;Splunk converts timestamps into a common time zone when they are received and the converts them to the user's preferred time zone at display time.&amp;nbsp; If a timestamp is in the wrong zone then it probably was ingested incorrectly.&lt;/P&gt;&lt;P&gt;Ideally, the timestamp of an event will contain zone information.&amp;nbsp; Failing that, the forwarder which sent the event can use the &lt;FONT face="courier new,courier"&gt;TZ&lt;/FONT&gt; setting in props.conf to specify the correct time zone.&lt;/P&gt;&lt;P&gt;Tell us more about the use case and we may be able to offer other solutions.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Mar 2021 12:23:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544609#M4899</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-03-20T12:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp; hosts scattered around th</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544641#M4900</link>
      <description>&lt;P&gt;To fix the TZ issue. Do I need to check the props.com on every host? So if the host is in a specific TZ &amp;amp; it is correctly set, then no worries. Due to 100s of hosts. So the TZ on a host is set correctly , there are worries right? I thought I could save time by not having to log into every available Host containing a Forwarder.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Mar 2021 19:24:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544641#M4900</guid>
      <dc:creator>SamHTexas</dc:creator>
      <dc:date>2021-03-20T19:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Best strategy to deal with / Fix Time zone (time_sych) issues between Splunk Servers &amp; hosts scattered around th</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544694#M4912</link>
      <description>&lt;P&gt;Yes, to correct the TZ issue, the props.conf settings on each forwarder must be examined.&amp;nbsp; If you have hundreds of hosts then you really should be using a Splunk deployment server (DS).&amp;nbsp; The DS offers a single point for monitoring and managing forwarders.&amp;nbsp; It saves tons of time by not having to sign in to each host to work on the forwarder.&lt;/P&gt;&lt;P&gt;See &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.1.2/Updating/Aboutdeploymentserver" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.1.2/Updating/Aboutdeploymentserver &lt;/A&gt;for more information about the DS.&lt;/P&gt;&lt;P&gt;I don't understand the question "So the TZ on a host is set correctly , there are worries right?".&amp;nbsp; There are two time zone settings - the one for the host and the one for Splunk Universal Forwarder.&amp;nbsp; We are concerned about the latter.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Mar 2021 18:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Best-strategy-to-deal-with-Fix-Time-zone-time-sych-issues/m-p/544694#M4912</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-03-21T18:07:53Z</dc:date>
    </item>
  </channel>
</rss>

