<?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: Route event data to different target groups issue in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366462#M92946</link>
    <description>&lt;P&gt;Hi belasker,&lt;/P&gt;

&lt;P&gt;If you read the docs for &lt;CODE&gt;outputs.conf&lt;/CODE&gt; &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Outputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Outputsconf&lt;/A&gt; you will find this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;defaultGroup = &amp;lt;target_group&amp;gt;, &amp;lt;target_group&amp;gt;, ...
* The forwarder sends all data to the specified groups.
* If you don't want to forward data automatically, don't set this attribute.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That said, as soon as you use the &lt;CODE&gt;defaultGroup&lt;/CODE&gt; in your &lt;CODE&gt;outputs.conf&lt;/CODE&gt; Splunk will send all events to the defined group.&lt;/P&gt;

&lt;P&gt;Hope that helps to understand the setting ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Sun, 07 May 2017 20:13:45 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2017-05-07T20:13:45Z</dc:date>
    <item>
      <title>Route event data to different target groups issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366461#M92945</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;BR /&gt;
here are my 3 configuration files transforms,props,outputs&lt;/P&gt;

&lt;P&gt;/// props.conf&lt;BR /&gt;
[host:firstClient]&lt;BR /&gt;
TRANSFORMS-routing=apacheWindows&lt;/P&gt;

&lt;P&gt;[host:secondClient]&lt;BR /&gt;
TRANSFORMS-routing=apacheLinux&lt;/P&gt;

&lt;P&gt;/// transforms.conf&lt;BR /&gt;
[apacheWindows]&lt;BR /&gt;
REGEX= .&lt;BR /&gt;
DEST_KEY=_TCP_ROUTING&lt;BR /&gt;
FORMAT=apacheWindows&lt;/P&gt;

&lt;P&gt;[apacheLinux]&lt;BR /&gt;
REGEX= .&lt;BR /&gt;
DEST_KEY=_TCP_ROUTING&lt;BR /&gt;
FORMAT=apacheLinux&lt;/P&gt;

&lt;P&gt;// outputs.conf&lt;BR /&gt;
[tcpout]&lt;BR /&gt;
defaultGroup = default-group&lt;/P&gt;

&lt;P&gt;[tcpout:apacheWindows]&lt;BR /&gt;
server=192.168.1.25:9997&lt;/P&gt;

&lt;P&gt;[tcpout:apacheLinux]&lt;BR /&gt;
server=192.168.1.24:9997&lt;/P&gt;

&lt;P&gt;[tcpout:default-group]&lt;BR /&gt;
server=192.168.1.25:9997&lt;/P&gt;

&lt;P&gt;the issue here is when i use default-group all the data will be forwarded to the default-group address even tcpout:apacheLinux&lt;BR /&gt;
and when i remove default-group from outputs.conf ,data is forwaded correctly to the 2 different indexers&lt;/P&gt;

&lt;P&gt;here the example that i have followed in splunk official documentation &lt;/P&gt;

&lt;P&gt;/////&lt;/P&gt;

&lt;P&gt;[tcpout]&lt;BR /&gt;
defaultGroup=everythingElseGroup&lt;/P&gt;

&lt;P&gt;[tcpout:syslogGroup]&lt;BR /&gt;
server=10.1.1.197:9996, 10.1.1.198:9997&lt;/P&gt;

&lt;P&gt;[tcpout:errorGroup]&lt;BR /&gt;
server=10.1.1.200:9999&lt;/P&gt;

&lt;P&gt;[tcpout:everythingElseGroup]&lt;BR /&gt;
server=10.1.1.250:6666&lt;BR /&gt;
syslogGroup and errorGroup receive events according to the rules specified in transforms.conf. All other events get routed to the default group, everythingElseGroup.&lt;/P&gt;

&lt;P&gt;//////&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:58:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366461#M92945</guid>
      <dc:creator>belasker</dc:creator>
      <dc:date>2020-09-29T13:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: Route event data to different target groups issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366462#M92946</link>
      <description>&lt;P&gt;Hi belasker,&lt;/P&gt;

&lt;P&gt;If you read the docs for &lt;CODE&gt;outputs.conf&lt;/CODE&gt; &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Outputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Outputsconf&lt;/A&gt; you will find this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;defaultGroup = &amp;lt;target_group&amp;gt;, &amp;lt;target_group&amp;gt;, ...
* The forwarder sends all data to the specified groups.
* If you don't want to forward data automatically, don't set this attribute.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That said, as soon as you use the &lt;CODE&gt;defaultGroup&lt;/CODE&gt; in your &lt;CODE&gt;outputs.conf&lt;/CODE&gt; Splunk will send all events to the defined group.&lt;/P&gt;

&lt;P&gt;Hope that helps to understand the setting ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Sun, 07 May 2017 20:13:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366462#M92946</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2017-05-07T20:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Route event data to different target groups issue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366463#M92947</link>
      <description>&lt;P&gt;Thank you but  In splunk official documentation (last example) they said " All other events get routed to the default group, everythingElseGroup" that means syslogGroup and errorGroup will be forwarded to the right place not the defaultgroup.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 09:12:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Route-event-data-to-different-target-groups-issue/m-p/366463#M92947</guid>
      <dc:creator>belasker</dc:creator>
      <dc:date>2017-05-08T09:12:23Z</dc:date>
    </item>
  </channel>
</rss>

