Deployment Architecture

Index Large File

rgaleone1
Path Finder

Context:
When attempting to index a massive log (>30GB) I am not seeing Splunk log percent complete, status, or errors in the _internal index. I see the tailingprocessor adding watch on my path, but I never see an end log when/if the file indexing in complete.

Ask:
Is the _internal index the location I should be looking for errors/success/status logs?

Tags (2)
0 Karma
1 Solution

Ayn
Legend

The best place to look might be in the TailingProcessor's own status endpoint. There you can see which status each monitor input currently has. Read more about it here: http://blogs.splunk.com/2011/01/02/did-i-miss-christmas-2/

View solution in original post

0 Karma

Ayn
Legend

The best place to look might be in the TailingProcessor's own status endpoint. There you can see which status each monitor input currently has. Read more about it here: http://blogs.splunk.com/2011/01/02/did-i-miss-christmas-2/

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!

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