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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...