Getting Data In

Programmatically determine data processed by splunk forwarder file reader

onelog2012
New Member

How can we programmatically determine which lines of a log file have been successfully processed by a splunk forwarder log reader? With this information, we will be able to rollover and cleanup files quickly and know there is no data loss.

Tags (1)
0 Karma

kristian_kolb
Ultra Champion

Ayn has a good point but you might also want to consider using indexer acknowledgement in combination with batch processing of the input files. With indexer acknowledgement, the indexer sends an acknowledgement when a piece of data has been written to disk in an index. Until then the forwarder keeps it in its output queue, and will resend it until it gets an acknowledgement. Pretty much like TCP network communications.

Batch reading of files (as opposed to monitoring) is a destructive method where a file is deleted after it has been processed (i.e. indexed).

More information on this can be found here:

Indexer Acknowledgement
http://docs.splunk.com/Documentation/Splunk/5.0/Deploy/Protectagainstlossofin-flightdata

Batch reading
http://docs.splunk.com/Documentation/Splunk/4.3.2/Data/Editinputs.conf

Hope this helps,

Kristian

Ayn
Legend

This should be of great interest to you: http://blogs.splunk.com/2011/01/02/did-i-miss-christmas-2/

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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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 ...