Getting Data In

Splunk Light Forwarder - Maximum file size for a monitored file?

g3s1oa
Explorer

Hi,

We have a splunk light forwarder monitoring a file that grows in excess of 5GB a day before rolling over. The roll over threshold cannot be changed. Splunk is having issues indexing this file and often time misses data, completely stops indexing data for this source (although other sources on the box seem fine) or indexes data on a different date than when the log was written. (for instance, an event will be written to the log on the 17th, but it will show up on our search head as the 14th or 15th). Unfortunately, there is only a time in the log and not a date.

Does anyone know if there is a maximum size a log can be for Splunk to still successfully monitor and forward that log? Is there an easy work around to the issue of the date not being present in the log?

Thanks!

delink
Communicator

With the date not present in the log, your best option is to have the filename being read have the date encoded in it somewhere.

Check out http://docs.splunk.com/Documentation/Splunk/6.0/Data/HowSplunkextractstimestamps for more details.

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...