<?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: Clone new Sourcetype from default in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92424#M19193</link>
    <description>&lt;P&gt;Not from the GUI no, but you can find the [log4j] stanza in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt; and just copy it to &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/props.conf&lt;/CODE&gt;. Then you just edit the stanza header &lt;CODE&gt;[log4j]&lt;/CODE&gt; to &lt;CODE&gt;[my_log4j]&lt;/CODE&gt; in the new location.&lt;/P&gt;

&lt;P&gt;Beware if there are any settings happening in &lt;CODE&gt;transforms.conf&lt;/CODE&gt; (like &lt;CODE&gt;REPORT&lt;/CODE&gt; or &lt;CODE&gt;TRANSFORMS&lt;/CODE&gt; directives in &lt;CODE&gt;props.conf&lt;/CODE&gt;) that you may also want to edit (if you want them to behave differently than for the original &lt;CODE&gt;[log4j]&lt;/CODE&gt;).  &lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
    <pubDate>Tue, 16 Oct 2012 19:59:07 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2012-10-16T19:59:07Z</dc:date>
    <item>
      <title>Clone new Sourcetype from default</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92423#M19192</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Is there a way to create / clone a new sourcetype say my_csv or my_log4j from the default sourcetype csv, log4j?
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Oct 2012 19:38:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92423#M19192</guid>
      <dc:creator>shangshin</dc:creator>
      <dc:date>2012-10-16T19:38:26Z</dc:date>
    </item>
    <item>
      <title>Re: Clone new Sourcetype from default</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92424#M19193</link>
      <description>&lt;P&gt;Not from the GUI no, but you can find the [log4j] stanza in &lt;CODE&gt;$SPLUNK_HOME/etc/system/default/props.conf&lt;/CODE&gt; and just copy it to &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/props.conf&lt;/CODE&gt;. Then you just edit the stanza header &lt;CODE&gt;[log4j]&lt;/CODE&gt; to &lt;CODE&gt;[my_log4j]&lt;/CODE&gt; in the new location.&lt;/P&gt;

&lt;P&gt;Beware if there are any settings happening in &lt;CODE&gt;transforms.conf&lt;/CODE&gt; (like &lt;CODE&gt;REPORT&lt;/CODE&gt; or &lt;CODE&gt;TRANSFORMS&lt;/CODE&gt; directives in &lt;CODE&gt;props.conf&lt;/CODE&gt;) that you may also want to edit (if you want them to behave differently than for the original &lt;CODE&gt;[log4j]&lt;/CODE&gt;).  &lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Tue, 16 Oct 2012 19:59:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92424#M19193</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-10-16T19:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: Clone new Sourcetype from default</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92425#M19194</link>
      <description>&lt;P&gt;I found the csv stanza ni default.prop.conf&lt;/P&gt;

&lt;P&gt;[csv]&lt;BR /&gt;
SHOULD_LINEMERGE = False&lt;BR /&gt;
pulldown_type = true&lt;BR /&gt;
CHECK_FOR_HEADER = true&lt;BR /&gt;
KV_MODE = none&lt;/P&gt;

&lt;P&gt;Assuming I want to change the standard delimiter from comma , to semi-colon ; based on this csv stanza, is it feasible?&lt;/P&gt;

&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:38:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92425#M19194</guid>
      <dc:creator>shangshin</dc:creator>
      <dc:date>2020-09-28T12:38:29Z</dc:date>
    </item>
    <item>
      <title>Re: Clone new Sourcetype from default</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92426#M19195</link>
      <description>&lt;P&gt;Yes. Take a look at DELIMS and FIELDS directives for transforms.conf. They should be put in a transforms.conf stanza which is called from props.conf through a REPORT-directive.&lt;/P&gt;

&lt;P&gt;I believe you should use &lt;CODE&gt;DELIMS = ";"&lt;CODE&gt;, with &lt;CODE&gt;FIELDS = field1, field2&lt;/CODE&gt; etc.&lt;/CODE&gt;&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2012 20:41:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Clone-new-Sourcetype-from-default/m-p/92426#M19195</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-10-17T20:41:57Z</dc:date>
    </item>
  </channel>
</rss>

