All Apps and Add-ons

Updating Splunkbase apps in Distributed Environment

wwhite12
Path Finder

When upgrading apps/add-ons in a distributed environment, is there a recommended best practice or is it similar to deploying the app initially where I can just paste the newer downloaded version from Splunkbase over the existing app and then push the new bundle to the peers to fully update the app? And also is there any scenario where a rolling restart for this wouldn’t be required?

Thanks in advance

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

You have the right method for updating apps.
See $SPLUNK_HOME/etc/system/default/app.conf for which config files do not require a rolling restart. The settings are described in $SPLUNK_HOME/etc/system/README/app.conf.spec.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

You have the right method for updating apps.
See $SPLUNK_HOME/etc/system/default/app.conf for which config files do not require a rolling restart. The settings are described in $SPLUNK_HOME/etc/system/README/app.conf.spec.

---
If this reply helps you, Karma would be appreciated.
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...