When changing an app's name via the Splunk web interface ('Manage Apps' > 'Edit Properties'), the app's name is only changed on the search head cluster node on which I'm working. When running
/opt/splunk/bin/splunk show shcluster-status
I see that the 'last_conf_replication' dates are recent, and already should have synced the change for the app's name among the other search head cluster nodes. When checking the app's name on the other nodes, I see that the name however has not changed.
What am I missing here? Are name changes of apps not replicated among the cluster? Or should I edit the specific 'app.conf' on the deployer, and push the configuration bundle?
Hi. I'm not sure why the name change isn't replicating, but in general I would say making changes and deploying config from the deployer would always be the best option, as opposed to making changes on configuration locally.
Hi. I'm not sure why the name change isn't replicating, but in general I would say making changes and deploying config from the deployer would always be the best option, as opposed to making changes on configuration locally.
Hello,
When I am updating apps in Search Head Cluster, I made my changes to an app on the deployer under this directory:
/opt/splunk/etc/shcluster/apps/
Then I distribute the configuration bundle:
/opt/splunk/bin/splunk apply shcluster-bundle -target https://sh01:8089
Have a look to this doc for more details:
http://docs.splunk.com/Documentation/Splunk/6.6.0/DistSearch/PropagateSHCconfigurationchanges
Regards