Deployment Architecture

how to manually control app config reload of specific deployment client



I have several critical UF/HF that providing equivalent service in a load-balanced topology.
I would like to leverage deployment server / client feature to push the configuration to them, but would like to control when a given DS client will really download/apply the config.
For example, I have 3 nodes acting as load-balanced HTTP Event Collector. I would like to trigger the update through DS of one node, wait the node to apply the change, before proceeding with others.

Questions :
- is it possible to disable automatic config update of a given instance (Splunk Enterprise or UF)
- then is there a command that can be run locally or remotely to trigger the usual DS client refresh on-demand/manually


0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...