I am have a simple app which just has this config in /default/limits.conf
[thruput] maxKBps = 0
How can we get this event?
06-29-2016 20:32:01.257 +0000 INFO ThruputProcessor - Current data throughput (258 kb/s) has reached maxKBps. As a result, data forwarding may be throttled. Consider increasing the value of maxKBps in limits.conf.
Should be unlimited?
The only other limits.conf I have is the default
[root@MYSERVER apps]# find . -name limits.conf ./SplunkUniversalForwarder/default/limits.conf ./TA-COMPANY-int-limits.conf-thruput-unilimited/default/limits.conf [root@MYSERVER apps]#
UF version is 6.3.3
the value of the
# Version 6.4.1 [thruput] maxKBps = 256
and this take precedence over your TA 😉 S before T ...
Learn more about the Splunk config precedence here http://docs.splunk.com/Documentation/Splunk/6.4.1/Admin/Wheretofindtheconfigurationfiles
and / or use
btool to check the applied config:
/opt/splunkforwarder/bin/splunk btool limits list thruput --debug
Hope this helps ...
Correct me if I'm wrong though but it WILL take precedence if you put limits.conf in the app/local/ folder of the app you want to control limits.conf with. So you could quick fix it my moving limits.conf to the local folder of your unlimited TA and restarting splunkd.
Just a thought though 😃
@tkwaller : Yes, that would quick fix it as you can see here 😉
/opt/splunkforwarder/bin/splunk btool limits list thruput --debug /opt/splunkforwarder/etc/apps/TA-COMPANY-int-limits.conf-thruput-unilimited/local/limits.conf [thruput] /opt/splunkforwarder/etc/apps/TA-COMPANY-int-limits.conf-thruput-unilimited/local/limits.conf maxKBps = 0