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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...