<?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: How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/638735#M15935</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161668"&gt;@ndavis4&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Yes, it is possible to have configuration like outputs.conf pushed out via the deployer but it would still end up in an app space under SPLUNK_HOME/etc/apps, not under&amp;nbsp;&amp;nbsp;SPLUNK_HOME/etc/system/local.&amp;nbsp; This is fine and would work, just watch out for any potential app and conf file precedence issues if there is more than one copy.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Apr 2023 00:35:39 GMT</pubDate>
    <dc:creator>yeahnah</dc:creator>
    <dc:date>2023-04-05T00:35:39Z</dc:date>
    <item>
      <title>How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636408#M15865</link>
      <description>&lt;P&gt;I am trying to distribute&amp;nbsp;$SPLUNK_HOME/etc/system/local/web.conf file to all my servers in my cluster with the&amp;nbsp; (search heads, management nodes, search peers). I want to change the name of my cert files from the default&lt;BR /&gt;&lt;BR /&gt;privKeyPath = $SPLUNK_HOME/etc/auth/splunkweb/privkey.pem&lt;BR /&gt;serverCert = $SPLUNK_HOME/etc/auth/splunkweb/cert.pem&lt;/P&gt;
&lt;P&gt;I am using the following command.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;splunk apply shcluster-bundle -target &amp;lt;URI&amp;gt;:&amp;lt;management_port&amp;gt; -auth &amp;lt;username&amp;gt;:&amp;lt;password&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I have searched and found nothing on how to do this. Only for apps ($SPLUNK_HOME/etc/apps/)&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 22:23:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636408#M15865</guid>
      <dc:creator>ndavis4</dc:creator>
      <dc:date>2023-03-28T22:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636411#M15866</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161668"&gt;@ndavis4&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Sorry, but this is not possible as the SHC deployer will only update apps in&amp;nbsp;&lt;SPAN&gt;$SPLUNK_HOME/etc/apps/.&lt;BR /&gt;&lt;BR /&gt;Some sort of automation (e.g. Ansible, Puppet) is better for this sort of config change, or as it's fairly static once changed, just work through each server and update manually.&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 21:45:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636411#M15866</guid>
      <dc:creator>yeahnah</dc:creator>
      <dc:date>2023-03-28T21:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636420#M15867</link>
      <description>&lt;P&gt;Thanks. This is what I expected. No problem, it is a static change and I can make changes on each server.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 22:25:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636420#M15867</guid>
      <dc:creator>ndavis4</dc:creator>
      <dc:date>2023-03-28T22:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636769#M15896</link>
      <description>&lt;P&gt;This is interesting.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.2/DistSearch/Forwardsearchheaddata" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.2/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Discusses how to forward internal logs from search head cluster members. It appears to recommend using the deployer to propagate the outputs.conf file. The outputs.conf files sits in&amp;nbsp;&lt;SPAN&gt;$SPLUNK_HOME/etc/system/local folder which the deployer can not propagate to. Am I reading this wrong?&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;H2&gt;&lt;SPAN class=""&gt;Forward data from search head cluster members&lt;/SPAN&gt;&lt;/H2&gt;&lt;P&gt;You perform the same configuration steps to forward data from search head cluster members to their set of search peers. However, you must ensure that all members use the same&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;outputs.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file. To do so, do not edit the file on the individual search heads.&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;Instead, use the deployer to propagate the file across the cluster.&lt;/EM&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2023 19:16:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/636769#M15896</guid>
      <dc:creator>ndavis4</dc:creator>
      <dc:date>2023-03-30T19:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to use deployer to distribute $SPLUNK_HOME/etc/system/local config files</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/638735#M15935</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161668"&gt;@ndavis4&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Yes, it is possible to have configuration like outputs.conf pushed out via the deployer but it would still end up in an app space under SPLUNK_HOME/etc/apps, not under&amp;nbsp;&amp;nbsp;SPLUNK_HOME/etc/system/local.&amp;nbsp; This is fine and would work, just watch out for any potential app and conf file precedence issues if there is more than one copy.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2023 00:35:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-use-deployer-to-distribute-SPLUNK-HOME-etc-system-local/m-p/638735#M15935</guid>
      <dc:creator>yeahnah</dc:creator>
      <dc:date>2023-04-05T00:35:39Z</dc:date>
    </item>
  </channel>
</rss>

