<?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: Convert a Sourcetype in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Convert-a-Sourcetype/m-p/94152#M19598</link>
    <description>&lt;P&gt;1.Splunk automagically sourcetypes some input methods (not all ie TCP, UDP) as data comes into Splunk at Index time.  Check out:&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
However, as you state, one of the places you can override automatic sourcetyping is in your inputs.conf file.  &lt;/P&gt;

&lt;P&gt;2.Since sourcetype is an indexed field you would have to clean out the index and re-index the data with your inputs.conf edits. This may not be practical in a production environment, original data sources, missing, etc ...  &lt;/P&gt;

&lt;P&gt;You should probably leverage sourcetype renaming (aliasing) instead for your boss. This can done via your Manager view -&amp;gt; Fields view -&amp;gt; sourcetype renaming. It is retroactive and takes place at search time. This "renamed field" would also be a knowledge object that could be private just for your boss, anyone with access to the app or global.  &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes&lt;/A&gt;  &lt;/P&gt;</description>
    <pubDate>Fri, 12 Jul 2013 22:01:23 GMT</pubDate>
    <dc:creator>rroberts</dc:creator>
    <dc:date>2013-07-12T22:01:23Z</dc:date>
    <item>
      <title>Convert a Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Convert-a-Sourcetype/m-p/94151#M19597</link>
      <description>&lt;P&gt;All, &lt;/P&gt;

&lt;P&gt;I only use Splunk about once a month, tops. So Please help me out if I use the wrong terms. &lt;/P&gt;

&lt;P&gt;I have a "app" which was written by my boss that is pulling in logs from our Siebel CRM servers. it does not specify a sourcetype in the inputs.conf file. My boss would like me to create a sourcetype for Siebel data. &lt;/P&gt;

&lt;P&gt;1) How do I create a "sourcetype"&lt;BR /&gt;
2) How do I convert the old automagically created sourcetype to my new one? &lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2013 21:23:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Convert-a-Sourcetype/m-p/94151#M19597</guid>
      <dc:creator>dwilson333</dc:creator>
      <dc:date>2013-07-12T21:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Convert a Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Convert-a-Sourcetype/m-p/94152#M19598</link>
      <description>&lt;P&gt;1.Splunk automagically sourcetypes some input methods (not all ie TCP, UDP) as data comes into Splunk at Index time.  Check out:&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
However, as you state, one of the places you can override automatic sourcetyping is in your inputs.conf file.  &lt;/P&gt;

&lt;P&gt;2.Since sourcetype is an indexed field you would have to clean out the index and re-index the data with your inputs.conf edits. This may not be practical in a production environment, original data sources, missing, etc ...  &lt;/P&gt;

&lt;P&gt;You should probably leverage sourcetype renaming (aliasing) instead for your boss. This can done via your Manager view -&amp;gt; Fields view -&amp;gt; sourcetype renaming. It is retroactive and takes place at search time. This "renamed field" would also be a knowledge object that could be private just for your boss, anyone with access to the app or global.  &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Renamesourcetypes&lt;/A&gt;  &lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2013 22:01:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Convert-a-Sourcetype/m-p/94152#M19598</guid>
      <dc:creator>rroberts</dc:creator>
      <dc:date>2013-07-12T22:01:23Z</dc:date>
    </item>
  </channel>
</rss>

