<?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: Can I configure defaultGroup when remotely deploying a *nix universal forwarder with a static configuration? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-configure-defaultGroup-when-remotely-deploying-a-nix/m-p/182074#M36478</link>
    <description>&lt;P&gt;The following configuration for any splunk enterprise version (not for universal forwarder)&lt;/P&gt;

&lt;P&gt;The below configuration send the data with sourcetype=mysourcetype to the  192.169.1.1 indexer and remaining data to 192.168.1.1 indexer. &lt;/P&gt;

&lt;P&gt;Hope this configuration helps you.&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[mysourcetype]&lt;BR /&gt;
TRANSFORMS-tcpfwd = sendtotcpreceiver&lt;/P&gt;

&lt;P&gt;transforms.conf&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[sendtotcpreceiver]&lt;BR /&gt;
REGEX = .&lt;BR /&gt;
DEST_KEY=_TCP_ROUTING &lt;BR /&gt;
FORMAT=tcpreceivergroup&lt;/P&gt;

&lt;P&gt;output.conf&lt;BR /&gt;&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[tcpout]&lt;BR /&gt;
defaultGroup = default-group&lt;/P&gt;

&lt;P&gt;[tcpout: default-group]&lt;BR /&gt;
server = 192.168.1.1:9997&lt;/P&gt;

&lt;P&gt;[tcpout:tcpreceivergroup]   &amp;lt;-- To Splunk indexer&lt;BR /&gt;
server=192.169.1.1:7999&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 18:37:29 GMT</pubDate>
    <dc:creator>jayannah</dc:creator>
    <dc:date>2020-09-28T18:37:29Z</dc:date>
    <item>
      <title>Can I configure defaultGroup when remotely deploying a *nix universal forwarder with a static configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-configure-defaultGroup-when-remotely-deploying-a-nix/m-p/182073#M36477</link>
      <description>&lt;P&gt;I am deploying universal forwarders with a bash script that is based on the sample script in &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/Remotelydeployanixdfwithastaticconfiguration"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/Remotelydeployanixdfwithastaticconfiguration&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;My issue is that defaultGroup is defaulted to "default-autolb-group" in splunkforwarder/etc/system/local/outputs.conf.&lt;/P&gt;

&lt;P&gt;I would like to default defaultGroup to "splunkcloud" rather than "default-autolb-group". Is there a Splunk-specific way to do that?&lt;/P&gt;

&lt;P&gt;This document mentions that there are CLI commands for customizing forwarding behavior, but I cannot find any detail beyond that: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/Configureforwarderswithoutputs.confd"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/Configureforwarderswithoutputs.confd&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I appreciate any help!&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jan 2015 01:13:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-configure-defaultGroup-when-remotely-deploying-a-nix/m-p/182073#M36477</guid>
      <dc:creator>will_paxata</dc:creator>
      <dc:date>2015-01-13T01:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can I configure defaultGroup when remotely deploying a *nix universal forwarder with a static configuration?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-I-configure-defaultGroup-when-remotely-deploying-a-nix/m-p/182074#M36478</link>
      <description>&lt;P&gt;The following configuration for any splunk enterprise version (not for universal forwarder)&lt;/P&gt;

&lt;P&gt;The below configuration send the data with sourcetype=mysourcetype to the  192.169.1.1 indexer and remaining data to 192.168.1.1 indexer. &lt;/P&gt;

&lt;P&gt;Hope this configuration helps you.&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[mysourcetype]&lt;BR /&gt;
TRANSFORMS-tcpfwd = sendtotcpreceiver&lt;/P&gt;

&lt;P&gt;transforms.conf&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[sendtotcpreceiver]&lt;BR /&gt;
REGEX = .&lt;BR /&gt;
DEST_KEY=_TCP_ROUTING &lt;BR /&gt;
FORMAT=tcpreceivergroup&lt;/P&gt;

&lt;P&gt;output.conf&lt;BR /&gt;&lt;BR /&gt;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;BR /&gt;
[tcpout]&lt;BR /&gt;
defaultGroup = default-group&lt;/P&gt;

&lt;P&gt;[tcpout: default-group]&lt;BR /&gt;
server = 192.168.1.1:9997&lt;/P&gt;

&lt;P&gt;[tcpout:tcpreceivergroup]   &amp;lt;-- To Splunk indexer&lt;BR /&gt;
server=192.169.1.1:7999&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:37:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-I-configure-defaultGroup-when-remotely-deploying-a-nix/m-p/182074#M36478</guid>
      <dc:creator>jayannah</dc:creator>
      <dc:date>2020-09-28T18:37:29Z</dc:date>
    </item>
  </channel>
</rss>

