<?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 Configure forwarding data to two tcpout groups without blocking on group failure. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Configure-forwarding-data-to-two-tcpout-groups-without-blocking/m-p/624619#M107367</link>
    <description>&lt;P&gt;Is it possible to configure heavy forwarders to send data to two tcpout groups (A,B) (outputs.conf) and don't&amp;nbsp; block on group B failure?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We want to send all data to group A, and a subset of data (specific sourcetypes) to group B, but group B is in a remote location and our link to that location is not fully stable and we don't want to event loss in group A on link failures or group B failures.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[tcpout]

[tcpout:groupA]
server=indexerA1_ip:9997,indexerA2_ip:9997

[tcpout:groupB]
server=indexerB_ip:9997&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Dec 2022 23:04:06 GMT</pubDate>
    <dc:creator>jg91</dc:creator>
    <dc:date>2022-12-16T23:04:06Z</dc:date>
    <item>
      <title>Configure forwarding data to two tcpout groups without blocking on group failure.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configure-forwarding-data-to-two-tcpout-groups-without-blocking/m-p/624619#M107367</link>
      <description>&lt;P&gt;Is it possible to configure heavy forwarders to send data to two tcpout groups (A,B) (outputs.conf) and don't&amp;nbsp; block on group B failure?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We want to send all data to group A, and a subset of data (specific sourcetypes) to group B, but group B is in a remote location and our link to that location is not fully stable and we don't want to event loss in group A on link failures or group B failures.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[tcpout]

[tcpout:groupA]
server=indexerA1_ip:9997,indexerA2_ip:9997

[tcpout:groupB]
server=indexerB_ip:9997&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2022 23:04:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configure-forwarding-data-to-two-tcpout-groups-without-blocking/m-p/624619#M107367</guid>
      <dc:creator>jg91</dc:creator>
      <dc:date>2022-12-16T23:04:06Z</dc:date>
    </item>
    <item>
      <title>Re: Configure forwarding data to two tcpout groups without blocking on group failure.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Configure-forwarding-data-to-two-tcpout-groups-without-blocking/m-p/624628#M107369</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/29622"&gt;@jg91&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;yes it should be possible: you have to configure a fork to send data to two groups of indexers following the instructons at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.2/Forwarding/Routeandfilterdatad#Filter_and_route_event_data_to_target_groups" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.2/Forwarding/Routeandfilterdatad#Filter_and_route_event_data_to_target_groups&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Sincerely I never tested this situation but If one group isn't available HF should cache those data and send them to the second group when available.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Sat, 17 Dec 2022 06:24:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Configure-forwarding-data-to-two-tcpout-groups-without-blocking/m-p/624628#M107369</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-12-17T06:24:53Z</dc:date>
    </item>
  </channel>
</rss>

