Splunk 4.1 should be easily able to handle hundreds of thousands of files, as long as only thousands of files are changing at the same time.
You can cause Splunk to reread its file input configuration by POSTing to https://splunk-server:8089/services/data/inputs/monitor/_reload
.
For example:
wget https://localhost:8089/services/data/inputs/monitor/_reload --post-data '' --no-check-certificate --user admin --password changeme -O -
For many cases the extracts in the props.conf can be reloaded by appending the following to a search -
| extract reload=true
This may work for transforms, if there is only a change to an existing setting, You would probably need to restart if you create a new setting in transforms.conf . Then again, it might not. I have had mixed results with many of these "on the fly" efforts. It is safest to restart.
Will this work with tranforms and props as well?
I believe the supported way is by doing a full restart. For some specific configuration changes in inputs.conf, a simple reload may not be sufficient. But Sorkin's answer will be very useful for me !
You could use splunk _internal call for this, instead of wget:
./splunk _internal call /services/data/inputs/monitor/_reload -auth admin:changeme
But I have not succeded to reload inputs.conf with this or with wget.
^ Also correct. I prefer the above as I don't have to hard code the pw when running from cli.
./splunk _internal call /services/data/inputs/monitor/_reload -auth
Will prompt you for Username: & Password: so you do not have to list them in your bash_history
Splunk 4.1+ can handle at least a few hundreds of thousands of files
Splunk 4.1 should be easily able to handle hundreds of thousands of files, as long as only thousands of files are changing at the same time.
You can cause Splunk to reread its file input configuration by POSTing to https://splunk-server:8089/services/data/inputs/monitor/_reload
.
For example:
wget https://localhost:8089/services/data/inputs/monitor/_reload --post-data '' --no-check-certificate --user admin --password changeme -O -
A restart is required.
See: http://www.splunk.com/base/Documentation/latest/Admin/Inputsconf
This section:
# There is an inputs.conf in $SPLUNK_HOME/etc/system/default/. To set custom configurations,
# place an inputs.conf in $SPLUNK_HOME/etc/system/local/. For examples, see inputs.conf.example.
# You must restart Splunk to enable new configurations.
The docs comments are actually incorrect. It is possible to reload inputs.conf without a restart. See Stephen Sorkin's answer