Getting Data In

Splunk Universal Forwarder Slow

ebay_nkitmitto
Engager

My Splunk forwarder is forwarding ~5 events per second (per my Deployment Monitor on my search head). The maxKBps is set to 20,000 and Splunk is transferring at a rate of 16,000 KBps. Why is the number of events so low? I have 27TB of data (and then some) that need to be indexed, these are historical log files.

I do have indexer acknowledgement enabled in my environment as well.

1 Solution

ebay_nkitmitto
Engager

By adding "maxQueueSize=500MB" to the outputs.conf file, under the [tcpout] stanza.

Change the 500MB to whatever you wish. It defaults to 500kb I believe. But be careful, because whatever you set this number to, it will consume 3x more RAM. So if you have it set to 500MB, it'll consume 1500MB of RAM.

Please this for more info (search for maxQueueSize):
http://docs.splunk.com/Documentation/Splunk/5.0.2/Admin/Outputsconf

View solution in original post

ebay_nkitmitto
Engager

By adding "maxQueueSize=500MB" to the outputs.conf file, under the [tcpout] stanza.

Change the 500MB to whatever you wish. It defaults to 500kb I believe. But be careful, because whatever you set this number to, it will consume 3x more RAM. So if you have it set to 500MB, it'll consume 1500MB of RAM.

Please this for more info (search for maxQueueSize):
http://docs.splunk.com/Documentation/Splunk/5.0.2/Admin/Outputsconf

Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...