<?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: props.conf not effective in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437466#M76320</link>
    <description>&lt;P&gt;Did you refresh or restart your splunk instance after the modifications ?&lt;/P&gt;</description>
    <pubDate>Mon, 12 Aug 2019 07:34:13 GMT</pubDate>
    <dc:creator>Kawtar</dc:creator>
    <dc:date>2019-08-12T07:34:13Z</dc:date>
    <item>
      <title>props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437462#M76316</link>
      <description>&lt;P&gt;Hi, this issue has been mentioned here before but still my changes in props.conf are not effective.&lt;BR /&gt;
Here is the configuration I'm using :&lt;/P&gt;

&lt;P&gt;Inputs.conf :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
host = bb1322454b5f
sourcetype=analyteacs_sales
source=splunk:8088
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Transforms.conf :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[clone_ebook_sales]

REGEX            = (?s).*
CLONE_SOURCETYPE = ebook_sales_for_resellers
DEST_KEY         = _MetaData:Index
FORMAT           = ebook_sales
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;A finally props.conf :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[analyteacs_sales]
TRANSFORMS-clone_ebook_sales = clone_ebook_sales
tz = Pacific/Fiji
sourcetype=ebook_sales
priority=100
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I tried to modify the system's timezone, but the changes aren't effective. Does someone see where it comes from?&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2019 16:11:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437462#M76316</guid>
      <dc:creator>juleserror</dc:creator>
      <dc:date>2019-08-09T16:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437463#M76317</link>
      <description>&lt;P&gt;What are you trying to accomplish?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2019 18:37:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437463#M76317</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-08-09T18:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437464#M76318</link>
      <description>&lt;P&gt;I try to change Splunk's system timezone (not the user's timezone) with the following property:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;tz = Pacific/Fiji
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But it's not taken into account.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2019 22:50:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437464#M76318</guid>
      <dc:creator>juleserror</dc:creator>
      <dc:date>2019-08-09T22:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437465#M76319</link>
      <description>&lt;P&gt;config files are case sensitive. tz should be TZ&lt;/P&gt;

&lt;P&gt;from docs:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TZ = &amp;lt;timezone identifier&amp;gt;
* The algorithm for determining the time zone for a particular event is as
  follows:
  * If the event has a timezone in its raw text (for example, UTC, -08:00),
  use that.
  * If TZ is set to a valid timezone string, use that.
  * If the event was forwarded, and the forwarder-indexer connection uses
  the version 6.0 and higher forwarding protocol, use the timezone provided
  by the forwarder.
  * Otherwise, use the timezone of the system that is running splunkd.
* Default: empty string
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can also troubleshoot what's being applied or not by using btool. just run:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;./splunk btool props list --debug analyteacs_sales&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;the result is all the attributes for you source type and their location look for TZ and check what is being applied there.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 01:34:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437465#M76319</guid>
      <dc:creator>diogofgm</dc:creator>
      <dc:date>2019-08-12T01:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437466#M76320</link>
      <description>&lt;P&gt;Did you refresh or restart your splunk instance after the modifications ?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 07:34:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437466#M76320</guid>
      <dc:creator>Kawtar</dc:creator>
      <dc:date>2019-08-12T07:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf not effective</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437467#M76321</link>
      <description>&lt;P&gt;After changing "tz" to "TZ" it works.&lt;BR /&gt;
Splunk CLI is a great tool !&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 07:57:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-not-effective/m-p/437467#M76321</guid>
      <dc:creator>juleserror</dc:creator>
      <dc:date>2019-08-13T07:57:54Z</dc:date>
    </item>
  </channel>
</rss>

