<?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 Issue with Indexing and Sourcetype in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-Indexing-and-Sourcetype/m-p/465537#M80249</link>
    <description>&lt;P&gt;Hello, I am using Splunk 7.2 and recently noticed a problem that I'm trying to figure out.   I am using Splunk universal forwarder to collect firewall logs from a local windows machine.   Logs are collecting fine and have been for quite some time.   I also configured Splunk to pull out the destination IP (as DestIP) from the firewall logs and this has been parsed out correctly for weeks.   Nothing has changed with my splunk configuration or windows configuration, but today I noticed that DestIP was no longer being parsed out.   I  also noticed that the sourcetype has changed.  Sourcetype used to be &lt;STRONG&gt;pffirewall&lt;/STRONG&gt;.  Today it started as &lt;STRONG&gt;pffirewall-too-small&lt;/STRONG&gt;.   I did some searches and saw that could be the case if there are too few logs, so I ran a ping to generate more than 100 logs.  Sourcename then changed to &lt;STRONG&gt;pffirewall-3&lt;/STRONG&gt;.   The filename that is being collected by universal forward has not changed, nor has the directory of the log location that it's being picked up from.   &lt;/P&gt;

&lt;P&gt;1) Why is the source name changing?&lt;BR /&gt;
2) How do I prevent this from happening again?&lt;/P&gt;

&lt;P&gt;Thank you..&lt;/P&gt;</description>
    <pubDate>Wed, 01 Apr 2020 18:26:00 GMT</pubDate>
    <dc:creator>matthewp486</dc:creator>
    <dc:date>2020-04-01T18:26:00Z</dc:date>
    <item>
      <title>Issue with Indexing and Sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-Indexing-and-Sourcetype/m-p/465537#M80249</link>
      <description>&lt;P&gt;Hello, I am using Splunk 7.2 and recently noticed a problem that I'm trying to figure out.   I am using Splunk universal forwarder to collect firewall logs from a local windows machine.   Logs are collecting fine and have been for quite some time.   I also configured Splunk to pull out the destination IP (as DestIP) from the firewall logs and this has been parsed out correctly for weeks.   Nothing has changed with my splunk configuration or windows configuration, but today I noticed that DestIP was no longer being parsed out.   I  also noticed that the sourcetype has changed.  Sourcetype used to be &lt;STRONG&gt;pffirewall&lt;/STRONG&gt;.  Today it started as &lt;STRONG&gt;pffirewall-too-small&lt;/STRONG&gt;.   I did some searches and saw that could be the case if there are too few logs, so I ran a ping to generate more than 100 logs.  Sourcename then changed to &lt;STRONG&gt;pffirewall-3&lt;/STRONG&gt;.   The filename that is being collected by universal forward has not changed, nor has the directory of the log location that it's being picked up from.   &lt;/P&gt;

&lt;P&gt;1) Why is the source name changing?&lt;BR /&gt;
2) How do I prevent this from happening again?&lt;/P&gt;

&lt;P&gt;Thank you..&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2020 18:26:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-with-Indexing-and-Sourcetype/m-p/465537#M80249</guid>
      <dc:creator>matthewp486</dc:creator>
      <dc:date>2020-04-01T18:26:00Z</dc:date>
    </item>
  </channel>
</rss>

