<?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 HF data forwarding to 3rd party design validation in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/HF-data-forwarding-to-3rd-party-design-validation/m-p/470147#M80856</link>
    <description>&lt;P&gt;I have a requirement to push a subset of universal and heavy forwarders originating data to a third party, for which I enabled a set of HFs for data forwarding alone.&lt;/P&gt;
&lt;P&gt;This is working fine, as data arrives uncooked to a target &lt;CODE&gt;syslog-ng&lt;/CODE&gt;.&lt;/P&gt;
&lt;P&gt;The troublesome part was being asked to ensure the HF resends the data in case the target undergoes maintenance, or has an outage lasting up to 2 days.&lt;/P&gt;
&lt;P&gt;Considering Persistent Queues don't work over &lt;CODE&gt;splunktcp&lt;/CODE&gt; streams, is it even an option for me to push uncooked data to the HFs, enabling a standard TCP input (not &lt;CODE&gt;splunktcp&lt;/CODE&gt;) with Persistent Queue enabled, say, to 200GB?&lt;/P&gt;
&lt;P&gt;Never heard of anyone using this approach.&lt;BR /&gt;Would this work?&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jun 2020 00:06:41 GMT</pubDate>
    <dc:creator>splunk_zen</dc:creator>
    <dc:date>2020-06-07T00:06:41Z</dc:date>
    <item>
      <title>HF data forwarding to 3rd party design validation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/HF-data-forwarding-to-3rd-party-design-validation/m-p/470147#M80856</link>
      <description>&lt;P&gt;I have a requirement to push a subset of universal and heavy forwarders originating data to a third party, for which I enabled a set of HFs for data forwarding alone.&lt;/P&gt;
&lt;P&gt;This is working fine, as data arrives uncooked to a target &lt;CODE&gt;syslog-ng&lt;/CODE&gt;.&lt;/P&gt;
&lt;P&gt;The troublesome part was being asked to ensure the HF resends the data in case the target undergoes maintenance, or has an outage lasting up to 2 days.&lt;/P&gt;
&lt;P&gt;Considering Persistent Queues don't work over &lt;CODE&gt;splunktcp&lt;/CODE&gt; streams, is it even an option for me to push uncooked data to the HFs, enabling a standard TCP input (not &lt;CODE&gt;splunktcp&lt;/CODE&gt;) with Persistent Queue enabled, say, to 200GB?&lt;/P&gt;
&lt;P&gt;Never heard of anyone using this approach.&lt;BR /&gt;Would this work?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 00:06:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/HF-data-forwarding-to-3rd-party-design-validation/m-p/470147#M80856</guid>
      <dc:creator>splunk_zen</dc:creator>
      <dc:date>2020-06-07T00:06:41Z</dc:date>
    </item>
  </channel>
</rss>

