https://community.splunk.com/t5/Deployment-Architecture/Universal-Forwarder-setting-maxKBps-via-cli/m-p/183333#M6845 <P>mrjsnook -<BR /> Your question is tagged with a universalforwarder tag; so two solutions, depending on your deployment. </P> <HR /> <OL> <LI><STRONG>Small deployments</STRONG>, use sed (assuming you are using *nix) to read in the current value of maxKBps from limits.conf and update the value. Alternatively, use the large deployment solution.</LI> <LI><STRONG>Large deployments</STRONG>, create an app for specifically updating maxKBps in limits.conf and push the conf file out to the nodes which require the update.</LI> </OL> <P><EM>Remember regardless of the path you choose, you must restart Splunk to enable configurations.</EM></P> <HR /> <P>To verify values Splunk is reading from all limits.conf files use:</P> <PRE><CODE> $SPLUNK_HOME/bin/splunk cmd btool limits list --debug </CODE></PRE> Thu, 19 Dec 2013 01:35:10 GMT rgaleone1 2013-12-19T01:35:10Z https://community.splunk.com/t5/Deployment-Architecture/Universal-Forwarder-setting-maxKBps-via-cli/m-p/183332#M6844 <P>I've looking around for a way to set maxKBps via cli. Most of the splunk answers suggest manually editing the limits.conf file but I'm looking for a way to do this programmatically. Anyone have any suggestion on how to do this?</P> <P>Thanks</P> Wed, 18 Dec 2013 15:27:11 GMT https://community.splunk.com/t5/Deployment-Architecture/Universal-Forwarder-setting-maxKBps-via-cli/m-p/183332#M6844 mrjsnook 2013-12-18T15:27:11Z https://community.splunk.com/t5/Deployment-Architecture/Universal-Forwarder-setting-maxKBps-via-cli/m-p/183333#M6845 <P>mrjsnook -<BR /> Your question is tagged with a universalforwarder tag; so two solutions, depending on your deployment. </P> <HR /> <OL> <LI><STRONG>Small deployments</STRONG>, use sed (assuming you are using *nix) to read in the current value of maxKBps from limits.conf and update the value. Alternatively, use the large deployment solution.</LI> <LI><STRONG>Large deployments</STRONG>, create an app for specifically updating maxKBps in limits.conf and push the conf file out to the nodes which require the update.</LI> </OL> <P><EM>Remember regardless of the path you choose, you must restart Splunk to enable configurations.</EM></P> <HR /> <P>To verify values Splunk is reading from all limits.conf files use:</P> <PRE><CODE> $SPLUNK_HOME/bin/splunk cmd btool limits list --debug </CODE></PRE> Thu, 19 Dec 2013 01:35:10 GMT https://community.splunk.com/t5/Deployment-Architecture/Universal-Forwarder-setting-maxKBps-via-cli/m-p/183333#M6845 rgaleone1 2013-12-19T01:35:10Z