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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...