Deploy or update Apps and configurations
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Contents
Deploy or update Apps and configurations
When you're ready to deploy a new or changed App or configuration out to deployment clients, use the Splunk CLI to tell deployment server that it has new content for its clients. Then, the next time the clients poll the deployment server, they'll know to pick up the new content.
To use Splunk's CLI, change to the $SPLUNK_HOME/bin/ directory and use the ./splunk command. (On Windows, you do not need to include the ./ beforehand.)
./splunk reload deploy-server
This command checks all server classes for a change, and notifies clients.
-or-
./splunk reload deploy-server -class <server class>
This command notifies and updates only the server class you specify. For example:
./splunk reload deploy-server -class www
This command notifies and updates only the clients that are members of the www server class.
Once a client receives configurations, it restarts splunkd and enables the relevant Apps if configured to do so in serviceclass.conf.
Confirm the deployment update
To confirm that all clients received the configuration correctly, check from the deployment server by using
./splunk list deploy-clients
This lists all the deployment clients and the last time they were successfully synced.
This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 View the Article History for its revisions.