<?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 Splunk UF Backlog in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494470#M84427</link>
    <description>&lt;P&gt;Hey everyone, quick UF question here... If a UF stops for whatever reason then comes back on later on, will the UF send the backlogs it missed while the service went offline?&lt;/P&gt;</description>
    <pubDate>Wed, 27 Nov 2019 15:58:15 GMT</pubDate>
    <dc:creator>johann2017</dc:creator>
    <dc:date>2019-11-27T15:58:15Z</dc:date>
    <item>
      <title>Splunk UF Backlog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494470#M84427</link>
      <description>&lt;P&gt;Hey everyone, quick UF question here... If a UF stops for whatever reason then comes back on later on, will the UF send the backlogs it missed while the service went offline?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 15:58:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494470#M84427</guid>
      <dc:creator>johann2017</dc:creator>
      <dc:date>2019-11-27T15:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF Backlog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494471#M84428</link>
      <description>&lt;P&gt;Hi @johann2017,&lt;BR /&gt;
yes: if connection with Indexer is interrupted, UF locally caches logs and send them as soon as connection is restored.&lt;/P&gt;

&lt;P&gt;If it's the UF itself to stop, when it restarts it ingest all the logs from the last ingested.&lt;/P&gt;

&lt;P&gt;There's only one situation when logs are lost and it's when I use an Heavy Forwarder to ingest syslogs but it's out of scope of your question.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 16:09:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494471#M84428</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-11-27T16:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF Backlog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494472#M84429</link>
      <description>&lt;P&gt;Yes, UFs will pick up where they left off.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 16:09:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494472#M84429</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-11-27T16:09:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF Backlog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494473#M84430</link>
      <description>&lt;P&gt;Thank you rich!&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 16:17:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-UF-Backlog/m-p/494473#M84430</guid>
      <dc:creator>johann2017</dc:creator>
      <dc:date>2019-11-27T16:17:20Z</dc:date>
    </item>
  </channel>
</rss>

