<?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: Managing Universal Forwarders and Indexers hosts in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Managing-Universal-Forwarders-and-Indexers-hosts/m-p/96912#M3569</link>
    <description>&lt;P&gt;Probably best to use a Deployment Server to manage outputs.conf across all your indexers.  Just build it as part of a deployed app.&lt;/P&gt;

&lt;P&gt;Lots of documentation on using a deployment server:&lt;/P&gt;

&lt;P&gt;[&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Deploy/Aboutdeploymentserver%5D%5B1"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Deploy/Aboutdeploymentserver][1&lt;/A&gt;]&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jul 2013 18:53:20 GMT</pubDate>
    <dc:creator>srioux</dc:creator>
    <dc:date>2013-07-16T18:53:20Z</dc:date>
    <item>
      <title>Managing Universal Forwarders and Indexers hosts</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Managing-Universal-Forwarders-and-Indexers-hosts/m-p/96911#M3568</link>
      <description>&lt;P&gt;What is the best way to manage universal forwarders and indexers at scale?&lt;/P&gt;

&lt;P&gt;By this I mean,  If I have 10 indexers today, I specify those on the universal forwarders configuration (outputs.conf).   If I add 3 new indexers will have to update every universal forwarder in my site?  &lt;/P&gt;

&lt;P&gt;This could be upwards to 200 machines running the universal forwarders that would need an update.  I've read a few times that using a loadbalancer is not a good solution to reduce the overhead of managing the indexers list.  &lt;/P&gt;

&lt;P&gt;What is the best way to manage the indexers list and configuration on the forwarders?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2013 18:22:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Managing-Universal-Forwarders-and-Indexers-hosts/m-p/96911#M3568</guid>
      <dc:creator>imosquera</dc:creator>
      <dc:date>2013-07-16T18:22:53Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Universal Forwarders and Indexers hosts</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Managing-Universal-Forwarders-and-Indexers-hosts/m-p/96912#M3569</link>
      <description>&lt;P&gt;Probably best to use a Deployment Server to manage outputs.conf across all your indexers.  Just build it as part of a deployed app.&lt;/P&gt;

&lt;P&gt;Lots of documentation on using a deployment server:&lt;/P&gt;

&lt;P&gt;[&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Deploy/Aboutdeploymentserver%5D%5B1"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Deploy/Aboutdeploymentserver][1&lt;/A&gt;]&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2013 18:53:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Managing-Universal-Forwarders-and-Indexers-hosts/m-p/96912#M3569</guid>
      <dc:creator>srioux</dc:creator>
      <dc:date>2013-07-16T18:53:20Z</dc:date>
    </item>
  </channel>
</rss>

