<?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 Universal Forwarder to report 2 Indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475395#M81608</link>
    <description>&lt;P&gt;What is the best way to route security events to Security Indexers and rest of the sourcetypes to operational indexers?&lt;/P&gt;

&lt;P&gt;And Can we manage universal forwarder with 2 deployment servers?&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2019 12:13:13 GMT</pubDate>
    <dc:creator>ansif</dc:creator>
    <dc:date>2019-09-11T12:13:13Z</dc:date>
    <item>
      <title>Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475395#M81608</link>
      <description>&lt;P&gt;What is the best way to route security events to Security Indexers and rest of the sourcetypes to operational indexers?&lt;/P&gt;

&lt;P&gt;And Can we manage universal forwarder with 2 deployment servers?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 12:13:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475395#M81608</guid>
      <dc:creator>ansif</dc:creator>
      <dc:date>2019-09-11T12:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475396#M81609</link>
      <description>&lt;P&gt;hI ansif,&lt;BR /&gt;
I answer first at the second question: you must set only one Deployment Server for a Universal Forwarder, you can have more Deployment Servers but  each one manage its UFs.&lt;BR /&gt;
about the way to send some events to an Indexer and some events to another one, you should see &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.1/Forwarding/Routeandfilterdatad#Route_inputs_to_specific_indexers_based_on_the_data_input" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.1/Forwarding/Routeandfilterdatad#Route_inputs_to_specific_indexers_based_on_the_data_input&lt;/A&gt; .&lt;BR /&gt;
In few words, you have to configure a fork in outputs.cof of your Universal Forwarders that defines the destination Indexers.&lt;BR /&gt;
Then in inputs.conf you can define which logs must be sent to Security indexers and which ones to other Indexers calling the stanzas in outputs.conf.&lt;BR /&gt;
Example&lt;BR /&gt;
In outputs.conf, create stanzas for each receiving indexer:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout:systemGroup]
server=server1:9997
[tcpout:secutityGroup]
server=server2:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In inputs.conf, specify _TCP_ROUTING to set the stanza in outputs.conf that each input should use for routing:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://.../file1.log]
_TCP_ROUTING = systemGroup
[monitor://.../file2.log]
_TCP_ROUTING = securityGroup
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:06:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475396#M81609</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-30T02:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475397#M81610</link>
      <description>&lt;P&gt;Hi @gcusello :&lt;/P&gt;

&lt;P&gt;Can we use Indexer discovery ? Like 2 master node details in the tcpout?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2019 07:50:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475397#M81610</guid>
      <dc:creator>ansif</dc:creator>
      <dc:date>2019-09-12T07:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475398#M81611</link>
      <description>&lt;P&gt;Yes, insted to address Indexers in outputs.conf, you can address Master Nodes' addresses and enable indexer discovery &lt;BR /&gt;
Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2019 08:01:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475398#M81611</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-09-12T08:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475399#M81612</link>
      <description>&lt;P&gt;Thanks @gcusello&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2019 08:10:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475399#M81612</guid>
      <dc:creator>ansif</dc:creator>
      <dc:date>2019-09-12T08:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475400#M81613</link>
      <description>&lt;P&gt;@gcusello : Just adding to it:&lt;/P&gt;

&lt;P&gt;Can we forward all default indexes like internal audit etc to both Indexers?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 16:06:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475400#M81613</guid>
      <dc:creator>ansif</dc:creator>
      <dc:date>2020-01-17T16:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475401#M81614</link>
      <description>&lt;P&gt;Yes, if you don't configure a default tcpout in outputs.conf and you don't insert _TCP_ROUTING in inputs.conf.&lt;BR /&gt;
This doesn't consume license but consumes storage, so you have to understand if you really need or not duplicating internal logs (I don't think!).&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:45:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475401#M81614</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-30T03:45:15Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder to report 2 Indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475402#M81615</link>
      <description>&lt;P&gt;The 2 instances are managed by 2 separate teams and both teams requires internal logs to troubleshoot.&lt;/P&gt;

&lt;P&gt;Thanks for the answer. I will goahead and test this. &lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 11:24:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-to-report-2-Indexer/m-p/475402#M81615</guid>
      <dc:creator>ansif</dc:creator>
      <dc:date>2020-02-20T11:24:36Z</dc:date>
    </item>
  </channel>
</rss>

