<?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 setting based on forwarder naming convention? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/timezone-setting-based-on-forwarder-naming-convention/m-p/494936#M84458</link>
    <description>&lt;P&gt;You just do this in props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host:.{number=character count preceding D, T, or P}D.*]
TZ=TZforDevHere
[host:.{number=character count preceding D, T, or P}T.*]
TZ=TZforTestHere
[host:.{number=character count preceding D, T, or P}P.*]
TZ=TZforProdHere
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Mon, 14 Oct 2019 03:12:43 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-10-14T03:12:43Z</dc:date>
    <item>
      <title>timezone setting based on forwarder naming convention?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timezone-setting-based-on-forwarder-naming-convention/m-p/494935#M84457</link>
      <description>&lt;P&gt;I'm sure Splunk'rs have ran across this already, so here's my issue.&lt;/P&gt;

&lt;P&gt;We have server naming conventions with "D" for DEV, "T" for TEST and "P" for PROD (in the same position of the server name). They reside in different data centers which are in different timezones. How do I set my props.conf to adjust the TZ value based on the naming convention of the host? The log sourcetypes are the same, going to the same index, but I need to adjust the TZ forward/back as these are in different data centers.&lt;/P&gt;

&lt;P&gt;Is this setting made with REGEX in the inputs.conf of the app? Or is this done in the props.conf? Confused on exactly where/how to do this. &lt;/P&gt;

&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 15:18:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timezone-setting-based-on-forwarder-naming-convention/m-p/494935#M84457</guid>
      <dc:creator>joesrepsolc</dc:creator>
      <dc:date>2019-10-10T15:18:54Z</dc:date>
    </item>
    <item>
      <title>Re: timezone setting based on forwarder naming convention?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timezone-setting-based-on-forwarder-naming-convention/m-p/494936#M84458</link>
      <description>&lt;P&gt;You just do this in props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host:.{number=character count preceding D, T, or P}D.*]
TZ=TZforDevHere
[host:.{number=character count preceding D, T, or P}T.*]
TZ=TZforTestHere
[host:.{number=character count preceding D, T, or P}P.*]
TZ=TZforProdHere
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 14 Oct 2019 03:12:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timezone-setting-based-on-forwarder-naming-convention/m-p/494936#M84458</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-10-14T03:12:43Z</dc:date>
    </item>
  </channel>
</rss>

