<?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: Sourcetype renaming itself! in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67313#M13528</link>
    <description>&lt;P&gt;i see. &lt;BR /&gt;
i deleted all the headers as the first time i indexed the file. they ran it in as an event line T_T&lt;BR /&gt;
but i ensured the rest of the logs were the same format as the first after i extracted my own fields. &lt;/P&gt;

&lt;P&gt;is there anyway to reverse it? i dont think i can simply reindex the same files now.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jun 2012 07:08:09 GMT</pubDate>
    <dc:creator>attgjh1</dc:creator>
    <dc:date>2012-06-05T07:08:09Z</dc:date>
    <item>
      <title>Sourcetype renaming itself!</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67311#M13526</link>
      <description>&lt;P&gt;ok. so i uploaded this log once. &lt;BR /&gt;
let's call it logA.csv with sourcetype: temp&lt;BR /&gt;
the monitor looks something like this: [ ...desktop\folder\logA.csv]&lt;/P&gt;

&lt;P&gt;so ive done my field extractions and everything and am pretty confident to get on with monitoring the entire directory. so i changed my monitor in inputs.conf to:&lt;BR /&gt;
[...desktop\folder\]&lt;BR /&gt;&lt;BR /&gt;
blacklist = *.xls&lt;BR /&gt;&lt;BR /&gt;
disabled = false&lt;BR /&gt;&lt;BR /&gt;
followTail = 0&lt;BR /&gt;&lt;BR /&gt;
sourcetype = temp&lt;/P&gt;

&lt;P&gt;and restarted splunk.&lt;/P&gt;

&lt;P&gt;now i have several sourcetypes inside: temp, temp-2, temp-3, temp-4&lt;/P&gt;

&lt;P&gt;is there anyway to fix this? temp-2, temp-3, temp-4 doesnt show up in props.conf at all as well. &lt;BR /&gt;
was there any step that went wrong?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2012 05:48:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67311#M13526</guid>
      <dc:creator>attgjh1</dc:creator>
      <dc:date>2012-06-05T05:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Sourcetype renaming itself!</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67312#M13527</link>
      <description>&lt;P&gt;This is a known feature of how Splunk treats CSV files. By default it will look for a header and extract the fields from that.&lt;/P&gt;

&lt;P&gt;If it finds files that differ a little bit in your directory, it will create a new sourcetype-&lt;EM&gt;n&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;There are a few posts here regarding this behaviour and how to fix it, here is one of them:&lt;BR /&gt;
&lt;A href="http://splunk-base.splunk.com/answers/24986/iis-log-fields-not-parsing"&gt;http://splunk-base.splunk.com/answers/24986/iis-log-fields-not-parsing&lt;/A&gt;&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;UPDATE:&lt;/P&gt;

&lt;P&gt;You can rename sourcetypes as well, it will not really change things that are already indexed, but you can access them using the same sourcetype name in your  searches. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Renamesourcetypes"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Renamesourcetypes&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Or you could use &lt;CODE&gt;sourcetype=temp*&lt;/CODE&gt; in your searches. &lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2012 07:03:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67312#M13527</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-06-05T07:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: Sourcetype renaming itself!</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67313#M13528</link>
      <description>&lt;P&gt;i see. &lt;BR /&gt;
i deleted all the headers as the first time i indexed the file. they ran it in as an event line T_T&lt;BR /&gt;
but i ensured the rest of the logs were the same format as the first after i extracted my own fields. &lt;/P&gt;

&lt;P&gt;is there anyway to reverse it? i dont think i can simply reindex the same files now.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2012 07:08:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67313#M13528</guid>
      <dc:creator>attgjh1</dc:creator>
      <dc:date>2012-06-05T07:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: Sourcetype renaming itself!</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67314#M13529</link>
      <description>&lt;P&gt;see update above. /k&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jun 2012 07:30:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sourcetype-renaming-itself/m-p/67314#M13529</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-06-05T07:30:27Z</dc:date>
    </item>
  </channel>
</rss>

