Is there a way to remotely manage data inputs, via configuration files pushed out by a deployment server?
I have perhaps 25-50 machines I will probably run Splunk on, and I need to know if it is possible to change the configuration settings for whole groups of servers at a time.
If so- could you point me in the right direction as to the process involved?
Yes. You would use the Deployment Server to push out new inputs.conf files to the clients, and restart splunkd. All inputs are defined in these files. Updating through the GUI or CLI updates these files in the same way, so appropriate files can be generated by direct editing, or by configuring a prototype and copying the resulting files.
Deployment Server is described here: http://www.splunk.com/base/Documentation/latest/Admin/Aboutdeploymentserver
The definition of the configuration files is the same configuring any other Splunk forwarder, regardless of whether deployment server is being used.
Yes. You would use the Deployment Server to push out new inputs.conf files to the clients, and restart splunkd. All inputs are defined in these files. Updating through the GUI or CLI updates these files in the same way, so appropriate files can be generated by direct editing, or by configuring a prototype and copying the resulting files.
Deployment Server is described here: http://www.splunk.com/base/Documentation/latest/Admin/Aboutdeploymentserver
The definition of the configuration files is the same configuring any other Splunk forwarder, regardless of whether deployment server is being used.
The above link seems dead. Updated link:
http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Aboutdeploymentserver