Splunk Search

Frequency lea updates pointer file

sdwilkerson
Contributor

Hello,

Does anyone know the frequency that the lea-loggrabber-splunk app's lea_loggrabber process should write to its record-number cache lea_log_rec_num.cache?

It seems that when Splunk is restarted or if lea_loggrabber is HUPd that this pointer file is not written to so next time the process starts, it gets lots of old data.

Also, a side note, is that because this pointer file is written to locally, you CANNOT use Splunk's Deployment Server to push this app since it will over write this record at each deployment/restart.

Thanks,

Sean

0 Karma
1 Solution

sdwilkerson
Contributor

Answering my own post here.
From what I can tell, the lea_log_rec_num.cache file only gets updated upon completion of the script run, meaning, the lea-connector has reached the end of the Checkpoint log file.

Therefore, in a high-volume environment, it could take a long time for this script to finish its initial run.

Sean

View solution in original post

sdwilkerson
Contributor

Answering my own post here.
From what I can tell, the lea_log_rec_num.cache file only gets updated upon completion of the script run, meaning, the lea-connector has reached the end of the Checkpoint log file.

Therefore, in a high-volume environment, it could take a long time for this script to finish its initial run.

Sean

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