<?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 How to avoid duplicated event in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75495#M15390</link>
    <description>&lt;P&gt;We have csv type of data file which is overwritten and with new data appended to the end every night.
I found Splunk load/duplicate all the data again everyday! &lt;/P&gt;

&lt;P&gt;As I know crcSalt only check CRC with first few lines of the file. How Splunk works in this case to identify only end of the file has new data?&lt;/P&gt;

&lt;P&gt;followTail works for file replace?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Apr 2011 14:59:01 GMT</pubDate>
    <dc:creator>hochit</dc:creator>
    <dc:date>2011-04-06T14:59:01Z</dc:date>
    <item>
      <title>How to avoid duplicated event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75495#M15390</link>
      <description>&lt;P&gt;We have csv type of data file which is overwritten and with new data appended to the end every night.
I found Splunk load/duplicate all the data again everyday! &lt;/P&gt;

&lt;P&gt;As I know crcSalt only check CRC with first few lines of the file. How Splunk works in this case to identify only end of the file has new data?&lt;/P&gt;

&lt;P&gt;followTail works for file replace?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2011 14:59:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75495#M15390</guid>
      <dc:creator>hochit</dc:creator>
      <dc:date>2011-04-06T14:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid duplicated event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75496#M15391</link>
      <description>&lt;P&gt;I am having the exact same issue!  did you figure out a solution?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2013 15:01:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75496#M15391</guid>
      <dc:creator>dlovett</dc:creator>
      <dc:date>2013-02-14T15:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid duplicated event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75497#M15392</link>
      <description>&lt;P&gt;How are you loading the file:&lt;/P&gt;

&lt;P&gt;Are you using a Splunk monitor?&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.1/Data/Monitorfilesanddirectories"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.1/Data/Monitorfilesanddirectories&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;That might be your problem.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2013 19:42:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-duplicated-event/m-p/75497#M15392</guid>
      <dc:creator>barne_dn</dc:creator>
      <dc:date>2013-02-14T19:42:55Z</dc:date>
    </item>
  </channel>
</rss>

