<?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 Updating Remote Forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38221#M7017</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have about 80 remote forwarders that forward back to a central Splunk server.  I was wondering if anyone had come up with a solution to updating these remote forwarders.  My desired functionality would be to be able to have the forwarder check a repository for the following:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;latest version of Splunk.  If the version in the repository is newer, upgrade.&lt;/LI&gt;
&lt;LI&gt;check props.conf &amp;amp; transforms.conf.  These differ slightly among the forwarders so I would have to be able to point to sub-types for the machines.&lt;/LI&gt;
&lt;LI&gt;check inputs.conf &amp;amp; update if newer.  However, in inputs.conf there is a hostname field that is different on every machine so this would have to be left alone.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I was starting to write something to accomplish this but it seems like this would be a common need so I was wondering if anyone had implemented something similar.&lt;/P&gt;

&lt;P&gt;Thanks for your help.&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;</description>
    <pubDate>Thu, 03 Feb 2011 22:32:30 GMT</pubDate>
    <dc:creator>kholleran</dc:creator>
    <dc:date>2011-02-03T22:32:30Z</dc:date>
    <item>
      <title>Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38221#M7017</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have about 80 remote forwarders that forward back to a central Splunk server.  I was wondering if anyone had come up with a solution to updating these remote forwarders.  My desired functionality would be to be able to have the forwarder check a repository for the following:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;latest version of Splunk.  If the version in the repository is newer, upgrade.&lt;/LI&gt;
&lt;LI&gt;check props.conf &amp;amp; transforms.conf.  These differ slightly among the forwarders so I would have to be able to point to sub-types for the machines.&lt;/LI&gt;
&lt;LI&gt;check inputs.conf &amp;amp; update if newer.  However, in inputs.conf there is a hostname field that is different on every machine so this would have to be left alone.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I was starting to write something to accomplish this but it seems like this would be a common need so I was wondering if anyone had implemented something similar.&lt;/P&gt;

&lt;P&gt;Thanks for your help.&lt;/P&gt;

&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2011 22:32:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38221#M7017</guid>
      <dc:creator>kholleran</dc:creator>
      <dc:date>2011-02-03T22:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38222#M7018</link>
      <description>&lt;P&gt;Great question.  I use the deployment server for keeping all the &lt;CODE&gt;.conf&lt;/CODE&gt; files updated, and I have a custom per-server app for a number of my boxes with unique inputs settings.  But, that's only half of your request.  We have a much small number of forwards, so for now I'm doing all of that by hand.  It would be possible to deploy a custom app with a "scripted input" script that downloads and installs the latest version (when needed), but there are tons of potential problems with that kind of approach; such as permissions, and failed/partial upgrades, in-use files, 32 vs 64 bit, tar/rpm/deb?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2011 23:06:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38222#M7018</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2011-02-03T23:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38223#M7019</link>
      <description>&lt;P&gt;Heres's a related idea:  &lt;A href="http://answers.splunk.com/questions/2567/need-deployment-server-to-assign-hostnames-dynamically-via-inputs-conf"&gt;http://answers.splunk.com/questions/2567/need-deployment-server-to-assign-hostnames-dynamically-via-inputs-conf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2011 23:10:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38223#M7019</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2011-02-03T23:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38224#M7020</link>
      <description>&lt;P&gt;Thanks for the link and suggestions.&lt;/P&gt;

&lt;P&gt;I ran into a bunch of issues with deployment server where it showed it was contacting the server but never actually pulled anything down, so I was planning to replace that with something else while also including the splunk installer.  All boxes in a group are the same, all are Windows.  I would want something that allowed it to install automatically after it was triggered by an admin.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2011 02:23:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38224#M7020</guid>
      <dc:creator>kholleran</dc:creator>
      <dc:date>2011-02-04T02:23:42Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38225#M7021</link>
      <description>&lt;P&gt;Have you considered using &lt;A href="http://www.puppetlabs.com/" rel="nofollow"&gt;Puppet&lt;/A&gt; or &lt;A href="http://www.opscode.com/" rel="nofollow"&gt;Chef&lt;/A&gt;?&lt;/P&gt;</description>
      <pubDate>Sat, 05 Feb 2011 05:15:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38225#M7021</guid>
      <dc:creator>msettipane</dc:creator>
      <dc:date>2011-02-05T05:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: Updating Remote Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38226#M7022</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;

&lt;P&gt;i know this is a old topic, but i want to now, do you found a good solution?&lt;/P&gt;

&lt;P&gt;thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2015 17:54:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Updating-Remote-Forwarders/m-p/38226#M7022</guid>
      <dc:creator>mbenitezr</dc:creator>
      <dc:date>2015-07-08T17:54:35Z</dc:date>
    </item>
  </channel>
</rss>

