<?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 monitored files being re-created often? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-monitored-files-being-re-created-often/m-p/585141#M102957</link>
    <description>&lt;P&gt;Ehh, I have an annoying case.&lt;/P&gt;
&lt;P&gt;I'm monitoring a file over windows share (to make things even worse to troubleshoot is that I don't have direct access to the share from my administrative user; only the domain user the UF is running with has access).&lt;/P&gt;
&lt;P&gt;The file is a CSV, it's getting properly split into fields, the date is getting parsed OK. I have transforms for removing the header (and a footer - this file has some footer as well). And this works mostly well.&lt;/P&gt;
&lt;P&gt;Mostly, because every time there is data added to the file, the file is apparently getting recreated from scratch - new data is inserted before footer and I'm getting entries like&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;02-15-2022&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;10&lt;/SPAN&gt;:55:23.008&lt;/SPAN&gt; +&lt;SPAN class=""&gt;0100&lt;/SPAN&gt; &lt;SPAN class=""&gt;INFO&lt;/SPAN&gt; &lt;SPAN class=""&gt;WatchedFile&lt;/SPAN&gt; &lt;SPAN class=""&gt;-&lt;/SPAN&gt; &lt;SPAN class=""&gt;File&lt;/SPAN&gt; &lt;SPAN class=""&gt;too&lt;/SPAN&gt; &lt;SPAN class=""&gt;small&lt;/SPAN&gt; &lt;SPAN class=""&gt;to&lt;/SPAN&gt; &lt;SPAN class=""&gt;check&lt;/SPAN&gt; &lt;SPAN class=""&gt;seekcrc&lt;/SPAN&gt;, &lt;SPAN class=""&gt;probably&lt;/SPAN&gt; &lt;SPAN class=""&gt;truncated.&lt;/SPAN&gt; &lt;SPAN class=""&gt;Will&lt;/SPAN&gt; &lt;SPAN class=""&gt;re-read&lt;/SPAN&gt; &lt;SPAN class=""&gt;entire&lt;/SPAN&gt; &lt;SPAN class=""&gt;file=&lt;/SPAN&gt;'&lt;SPAN class=""&gt;\\path\to\the\file'&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Luckily, for now the file is relatively small (some 3k lines) and doesn't eat up much license compared to this customer's other sources but it's annoying that the same events are getting ingested several times during the day.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;The problem is that I don't see any reasonable way to avoid it. There is no deduplication functionality on input, I don't have any "buffer" I could compare it with using ingest-time eval or something like that.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Any aces up your sleeves? &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Feb 2022 00:35:58 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2022-02-17T00:35:58Z</dc:date>
    <item>
      <title>How to avoid monitored files being re-created often?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-monitored-files-being-re-created-often/m-p/585141#M102957</link>
      <description>&lt;P&gt;Ehh, I have an annoying case.&lt;/P&gt;
&lt;P&gt;I'm monitoring a file over windows share (to make things even worse to troubleshoot is that I don't have direct access to the share from my administrative user; only the domain user the UF is running with has access).&lt;/P&gt;
&lt;P&gt;The file is a CSV, it's getting properly split into fields, the date is getting parsed OK. I have transforms for removing the header (and a footer - this file has some footer as well). And this works mostly well.&lt;/P&gt;
&lt;P&gt;Mostly, because every time there is data added to the file, the file is apparently getting recreated from scratch - new data is inserted before footer and I'm getting entries like&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;02-15-2022&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;10&lt;/SPAN&gt;:55:23.008&lt;/SPAN&gt; +&lt;SPAN class=""&gt;0100&lt;/SPAN&gt; &lt;SPAN class=""&gt;INFO&lt;/SPAN&gt; &lt;SPAN class=""&gt;WatchedFile&lt;/SPAN&gt; &lt;SPAN class=""&gt;-&lt;/SPAN&gt; &lt;SPAN class=""&gt;File&lt;/SPAN&gt; &lt;SPAN class=""&gt;too&lt;/SPAN&gt; &lt;SPAN class=""&gt;small&lt;/SPAN&gt; &lt;SPAN class=""&gt;to&lt;/SPAN&gt; &lt;SPAN class=""&gt;check&lt;/SPAN&gt; &lt;SPAN class=""&gt;seekcrc&lt;/SPAN&gt;, &lt;SPAN class=""&gt;probably&lt;/SPAN&gt; &lt;SPAN class=""&gt;truncated.&lt;/SPAN&gt; &lt;SPAN class=""&gt;Will&lt;/SPAN&gt; &lt;SPAN class=""&gt;re-read&lt;/SPAN&gt; &lt;SPAN class=""&gt;entire&lt;/SPAN&gt; &lt;SPAN class=""&gt;file=&lt;/SPAN&gt;'&lt;SPAN class=""&gt;\\path\to\the\file'&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Luckily, for now the file is relatively small (some 3k lines) and doesn't eat up much license compared to this customer's other sources but it's annoying that the same events are getting ingested several times during the day.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;The problem is that I don't see any reasonable way to avoid it. There is no deduplication functionality on input, I don't have any "buffer" I could compare it with using ingest-time eval or something like that.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Any aces up your sleeves? &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 00:35:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-avoid-monitored-files-being-re-created-often/m-p/585141#M102957</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-02-17T00:35:58Z</dc:date>
    </item>
  </channel>
</rss>

