<?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: UFs new pointer after restart in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521555#M88117</link>
    <description>&lt;P&gt;When the UF starts, it resumes reading log files from where it left off.&lt;/P&gt;&lt;P&gt;If the UF crashes, data read and not sent is lost unless indexer acknowledgment is used.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Sep 2020 20:24:41 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-09-25T20:24:41Z</dc:date>
    <item>
      <title>UFs new pointer after restart</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521550#M88116</link>
      <description>&lt;P&gt;If I gracefully shutdown the UF, it will send all logs from output queue and from internal parsing queue.&lt;/P&gt;&lt;P&gt;Suppose I restart the UF after 1min, will it start sending logs from logs file where he had left before shutdown???&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or will it start sending new logs which are getting appended independent of where had left off.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If in such scenarios logs are getting dropped, is there any way to detect how many such logs were dropped?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What may happen if UF is crashed, obviously it will drop queue logs but from where he would start once he is up and running??&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2020 19:41:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521550#M88116</guid>
      <dc:creator>hectorvp</dc:creator>
      <dc:date>2020-09-25T19:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: UFs new pointer after restart</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521555#M88117</link>
      <description>&lt;P&gt;When the UF starts, it resumes reading log files from where it left off.&lt;/P&gt;&lt;P&gt;If the UF crashes, data read and not sent is lost unless indexer acknowledgment is used.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2020 20:24:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521555#M88117</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-09-25T20:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: UFs new pointer after restart</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521612#M88129</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then if UF crashes and we restore it by some means and again UF is up and running ,although UF dropped events which was read but then from where he would start reading new events from the file??&lt;/P&gt;&lt;P&gt;Again would UF start from where he had left off??&lt;/P&gt;</description>
      <pubDate>Sat, 26 Sep 2020 15:37:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521612#M88129</guid>
      <dc:creator>hectorvp</dc:creator>
      <dc:date>2020-09-26T15:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: UFs new pointer after restart</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521615#M88131</link>
      <description>The UF will start from the last file position it saved.</description>
      <pubDate>Sat, 26 Sep 2020 16:39:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UFs-new-pointer-after-restart/m-p/521615#M88131</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-09-26T16:39:36Z</dc:date>
    </item>
  </channel>
</rss>

