<?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: Universal Forwarder and Offline Scenarios in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55167#M10747</link>
    <description>&lt;P&gt;To guard against loss of data when forwarding to an indexer, you can use Splunk's indexer acknowledgment capability. With indexer acknowledgment, the forwarder will resend any data not acknowledged as "received" by the indexer.&lt;/P&gt;

&lt;P&gt;This topic is discussed at length in the documentation link below.  &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Deploy/Protectagainstlossofin-flightdata"&gt;Protect against loss of in-flight data&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;About queues :&lt;/P&gt;

&lt;P&gt;Memory queues, used by default. A forwarder crashing/shutdown while queueing data will lose the data waiting in the memory queue.&lt;/P&gt;

&lt;P&gt;Persistent queues, you can configure your forwarders to keep part of the data queued on disk instead of memory, they will be resumed once restarted. &lt;/P&gt;

&lt;P&gt;see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Usepersistentqueues"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Usepersistentqueues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, this Splunk-base answer has some additional details:&lt;BR /&gt;
&lt;A href="http://splunk-base.splunk.com/answers/46073/does-the-indexer-acknowledgement-queuelist-persist-across-splunk-restarts"&gt;http://splunk-base.splunk.com/answers/46073/does-the-indexer-acknowledgement-queuelist-persist-across-splunk-restarts&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jun 2013 23:51:10 GMT</pubDate>
    <dc:creator>okrabbe_splunk</dc:creator>
    <dc:date>2013-06-04T23:51:10Z</dc:date>
    <item>
      <title>Universal Forwarder and Offline Scenarios</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55166#M10746</link>
      <description>&lt;P&gt;I am using Universal Forwarder on Windows machines to forward events generated by a script.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Question:&lt;/STRONG&gt; What happens if the indexer(s) cannot be reached for some reason? Are the events buffered locally and sent when the connection is restored? Is the behavior in this situation documented anywhere?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 20:59:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55166#M10746</guid>
      <dc:creator>helge</dc:creator>
      <dc:date>2013-06-04T20:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder and Offline Scenarios</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55167#M10747</link>
      <description>&lt;P&gt;To guard against loss of data when forwarding to an indexer, you can use Splunk's indexer acknowledgment capability. With indexer acknowledgment, the forwarder will resend any data not acknowledged as "received" by the indexer.&lt;/P&gt;

&lt;P&gt;This topic is discussed at length in the documentation link below.  &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Deploy/Protectagainstlossofin-flightdata"&gt;Protect against loss of in-flight data&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;About queues :&lt;/P&gt;

&lt;P&gt;Memory queues, used by default. A forwarder crashing/shutdown while queueing data will lose the data waiting in the memory queue.&lt;/P&gt;

&lt;P&gt;Persistent queues, you can configure your forwarders to keep part of the data queued on disk instead of memory, they will be resumed once restarted. &lt;/P&gt;

&lt;P&gt;see &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Usepersistentqueues"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/Data/Usepersistentqueues&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, this Splunk-base answer has some additional details:&lt;BR /&gt;
&lt;A href="http://splunk-base.splunk.com/answers/46073/does-the-indexer-acknowledgement-queuelist-persist-across-splunk-restarts"&gt;http://splunk-base.splunk.com/answers/46073/does-the-indexer-acknowledgement-queuelist-persist-across-splunk-restarts&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2013 23:51:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55167#M10747</guid>
      <dc:creator>okrabbe_splunk</dc:creator>
      <dc:date>2013-06-04T23:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder and Offline Scenarios</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55168#M10748</link>
      <description>&lt;P&gt;Thanks, that is helpful. However, the document does not discuss how much data the forwarder still accepts when it cannot reach an indexer (with acks enabled). Will it stop accepting once the queue is full? Or will it accept more? In that case, where is the data stored - in memory, or on disk?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 08:14:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55168#M10748</guid>
      <dc:creator>helge</dc:creator>
      <dc:date>2013-06-05T08:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder and Offline Scenarios</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55169#M10749</link>
      <description>&lt;P&gt;helge, I updated the answer to discuss using persistent queues.  Hopefully this is what you were looking for.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 13:15:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55169#M10749</guid>
      <dc:creator>okrabbe_splunk</dc:creator>
      <dc:date>2013-06-05T13:15:06Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder and Offline Scenarios</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55170#M10750</link>
      <description>&lt;P&gt;I think 25MB - &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.4/Forwarding/Protectagainstlossofin-flightdata"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.4/Forwarding/Protectagainstlossofin-flightdata&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2017 16:05:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-and-Offline-Scenarios/m-p/55170#M10750</guid>
      <dc:creator>jagadeeshm</dc:creator>
      <dc:date>2017-03-07T16:05:48Z</dc:date>
    </item>
  </channel>
</rss>

