<?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 Persistent queues splunktcp in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76528#M181471</link>
    <description>&lt;P&gt;Persistent queues are not available for splunktcp, &lt;BR /&gt;
I use several Forwarders on networks n, sending to a central forwarder on network A, from here all data goes to a central indexer, I would like to use persistent queueing for dataloss prevention. &lt;/P&gt;

&lt;P&gt;TCP/UPD/Syslog will work but not splunktcp.&lt;/P&gt;

&lt;P&gt;Is there a way for getting this to work?&lt;/P&gt;</description>
    <pubDate>Wed, 22 Feb 2012 16:45:39 GMT</pubDate>
    <dc:creator>SylviaB</dc:creator>
    <dc:date>2012-02-22T16:45:39Z</dc:date>
    <item>
      <title>Persistent queues splunktcp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76528#M181471</link>
      <description>&lt;P&gt;Persistent queues are not available for splunktcp, &lt;BR /&gt;
I use several Forwarders on networks n, sending to a central forwarder on network A, from here all data goes to a central indexer, I would like to use persistent queueing for dataloss prevention. &lt;/P&gt;

&lt;P&gt;TCP/UPD/Syslog will work but not splunktcp.&lt;/P&gt;

&lt;P&gt;Is there a way for getting this to work?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2012 16:45:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76528#M181471</guid>
      <dc:creator>SylviaB</dc:creator>
      <dc:date>2012-02-22T16:45:39Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent queues splunktcp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76529#M181472</link>
      <description>&lt;P&gt;SylviaB - How are you trying to set this up? What sort of error message are you getting to say that it isn't working? I have it working currently using the following syntax&lt;/P&gt;

&lt;P&gt;[splunktcp://9998]&lt;BR /&gt;
persistentQueueSize=100GB&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2012 00:56:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76529#M181472</guid>
      <dc:creator>jdunlea_splunk</dc:creator>
      <dc:date>2012-03-16T00:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent queues splunktcp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76530#M181473</link>
      <description>&lt;P&gt;We are also searching for more information regarding the usage of persistent queues for splunktcp.&lt;BR /&gt;
We want to avoid for example data loss during splunk update, where you need to stop the index cluster in case of major version update.&lt;BR /&gt;
So you will loss "live data" like it comes for excample fron the windows_TA and or unix_ta (CPU, Ram, disk, etc.)&lt;/P&gt;

&lt;P&gt;According to &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Usepersistentqueues:" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Usepersistentqueues:&lt;/A&gt;&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;Persistent queues are not available for these input types:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Monitor
Batch
File system change monitor
splunktcp (input from Splunk forwarders)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is the above mentioned option recommended, documented  and supported from splunk?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 08:42:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Persistent-queues-splunktcp/m-p/76530#M181473</guid>
      <dc:creator>glentes</dc:creator>
      <dc:date>2020-09-29T08:42:59Z</dc:date>
    </item>
  </channel>
</rss>

