Getting Data In

Splunk forwarder delays only Concurrently generated logs

gsonal03
New Member

After reviewing splund.log, metrics.log in several attempts and adding check on storage etc. on splunk servers, we have received one pattern.
The only logs getting delayed by forwarder are the one's generated by multiple threads in an application. We have several single threaded applications that generate huge logs, but they don't get delayed during indexing.
While the one app running parallel jobs in multiple threads and generating relatively less logs, still gets delayed in indexing.

Is there any throttle limit that can be adjusted for allowing more logs to get forwarded to indexers per second?

Tags (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...