<?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: easy way to change _TCP_ROUTING = * ????? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277587#M53237</link>
    <description>&lt;P&gt;Good answer but how to do this when you manage thousands of Universal Forwarder with the Deployment Server?&lt;/P&gt;</description>
    <pubDate>Wed, 18 Oct 2017 12:22:40 GMT</pubDate>
    <dc:creator>JuGuSm</dc:creator>
    <dc:date>2017-10-18T12:22:40Z</dc:date>
    <item>
      <title>easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277580#M53230</link>
      <description>&lt;P&gt;I'm working on doing some data cloning.&lt;/P&gt;

&lt;P&gt;As a first step, outputs.conf (on a virgin 6.4.1 universal forwarder on Windows) looks like this, and all is well.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = splunk-c-ix.local:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Data goes to splunk-c-ix just fine.&lt;/P&gt;

&lt;P&gt;When I add another output group (even without making it the default or referring to it in any _TCP_ROUTING lines), then _internal output starts going to both groups.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = splunk-c-ix.local:9997

[tcpout:clone-group]
server = splunk-c-hf.local:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I dug into it, and found &lt;CODE&gt;_TCP_ROUTING = *&lt;/CODE&gt; inside the &lt;CODE&gt;[monitor://...]&lt;/CODE&gt; stanzas inside $SPLUNK_HOME\apps\SplunkUniversalForwarder\defaults\inputs.conf, which accounts for the behaviour.&lt;/P&gt;

&lt;P&gt;I was hoping I could just do a blacklist for the _* indexes on the tcpout:clone-group, but the docs indicate that blacklist/whitelist only happens globally.&lt;/P&gt;

&lt;P&gt;Is there an easy way to override this besides hunting down all the &lt;CODE&gt;_TCP_ROUTING = *&lt;/CODE&gt; in the inputs.conf and overriding them in a local\inputs.conf? &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:20:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277580#M53230</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2020-09-29T10:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277581#M53231</link>
      <description>&lt;P&gt;Were you able to solve this?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 06:47:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277581#M53231</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2016-08-16T06:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277582#M53232</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;Have you tried to include this, in your system/local/inputs.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
_TCP_ROUTING = default-autolb-group
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It should override all default settings, to send default inputs just to the default group.&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 10:45:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277582#M53232</guid>
      <dc:creator>gfuente</dc:creator>
      <dc:date>2016-08-16T10:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277583#M53233</link>
      <description>&lt;P&gt;I hadn't receive gfuente's suggestion yet. which looks promising, I will have to see if it can be adapted to a deployment server fed environment (system/local/inputs.conf is not something that can be distributed via DS). That may be the way to go.&lt;/P&gt;

&lt;P&gt;Right now, I just added overrides to the _TCP_ROUTING for guilty [monitor://] stanzas in a deployed inputs.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:\Program Files\SplunkUniversalForwarder\etc\splunk.version]
_TCP_ROUTING = default-autolb-group

[monitor://C:\Program Files\SplunkUniversalForwarder\var\log\splunk\metrics.log]
_TCP_ROUTING = default-autolb-group

[monitor://C:\Program Files\SplunkUniversalForwarder\var\log\splunk\splunkd.log]
_TCP_ROUTING = default-autolb-group
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It's ugly and a little brittle (will need to watch future versions to see if they add monitor: stanzas, and someone will break me sooner or later by deploying Splunk onto the &lt;span class="lia-unicode-emoji" title=":anguished_face:"&gt;😧&lt;/span&gt; drive), but it works.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:38:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277583#M53233</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2020-09-29T10:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277584#M53234</link>
      <description>&lt;P&gt;will try this when I get a chance.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 12:03:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277584#M53234</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2016-08-16T12:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277585#M53235</link>
      <description>&lt;P&gt;This seems to work for most inputs but the _internal inputs remain unchanged this is output from &lt;BR /&gt;
/opt/splunkforwarder/bin/splunk btool inputs list&lt;/P&gt;

&lt;P&gt;[monitor:///opt/splunkforwarder/var/log/splunk/metrics.log]&lt;BR /&gt;
_TCP_ROUTING = *&lt;BR /&gt;
_rcvbuf = 1572864&lt;BR /&gt;
host = myVeryPersonalForwarder&lt;BR /&gt;
index = _internal&lt;/P&gt;

&lt;P&gt;Regards &lt;BR /&gt;
Chris&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:41:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277585#M53235</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2020-09-29T10:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277586#M53236</link>
      <description>&lt;P&gt;make sense that this wouldn't work. The _TCP_ROUTING in a [default] stanza would only be used if _TCP_ROUTING was not specified elsewhere, and _TCP_ROUTING &lt;EM&gt;is&lt;/EM&gt; specified elsewhere, so the [default] one gets ignored.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:39:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277586#M53236</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2020-09-29T10:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277587#M53237</link>
      <description>&lt;P&gt;Good answer but how to do this when you manage thousands of Universal Forwarder with the Deployment Server?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2017 12:22:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/277587#M53237</guid>
      <dc:creator>JuGuSm</dc:creator>
      <dc:date>2017-10-18T12:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: easy way to change _TCP_ROUTING = * ?????</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/710528#M117362</link>
      <description>&lt;P&gt;You can just create a .../local/inputs.conf with stanzas and attributes that override the default config like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[monitor://$SPLUNK_HOME/var/log/splunk/splunkd.log]
_TCP_ROUTING = default-autolb-group
index = _internal

[monitor://$SPLUNK_HOME/var/log/splunk/metrics.log]
_TCP_ROUTING = default-autolb-group
index = _internal&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Feb 2025 01:49:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/easy-way-to-change-TCP-ROUTING/m-p/710528#M117362</guid>
      <dc:creator>moliminous</dc:creator>
      <dc:date>2025-02-04T01:49:29Z</dc:date>
    </item>
  </channel>
</rss>

