Getting Data In

Splunk forwarder delays only Concurrently generated logs

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
Get Updates on the Splunk Community!

Ready, Set, SOAR: How Utility Apps Can Up Level Your Playbooks!

 WATCH NOW Powering your capabilities has never been so easy with ready-made Splunk® SOAR Utility Apps. Parse ...

DevSecOps: Why You Should Care and How To Get Started

 WATCH NOW In this Tech Talk we will talk about what people mean by DevSecOps and deep dive into the different ...

Introducing Ingest Actions: Filter, Mask, Route, Repeat

WATCH NOW Ingest Actions (IA) is the best new way to easily filter, mask and route your data in Splunk® ...