Getting Data In

I moved source data, they are not reindexed

wsw70
Communicator

Hello

I have two directories dir1 and dir2 monitored by splunk, new files in each directory are indexed, respectively, to index1 and index2.

I realized that I made a mistake and put myfile.txt in dir1 instead of dir2. The events within were indexed to index1, which is not a problem (I will deal with them later).

I then moved the file via mv dir1/myfile.txt dir2, the move was successful, I can now see myfile.txt in dir2 but the events are not visible in index2. Other files which are in this directory are indexed correctly, so indexing as it works fine.

Why moving the file did not trigger the indexing? From the standpoint of index2 these are new files and the fact that they have been previously indexed to index1 should not make any difference, right?

0 Karma
1 Solution

gfuente
Motivator

Hello

by default Splunk doesn´t use the path of the file to identify if the file has been already indexed. You have two options, make an small modification at the beggining of the file or add:

crcSalt = <SOURCE>

To your inputs.conf stanza.

Regards

View solution in original post

gfuente
Motivator

Hello

by default Splunk doesn´t use the path of the file to identify if the file has been already indexed. You have two options, make an small modification at the beggining of the file or add:

crcSalt = <SOURCE>

To your inputs.conf stanza.

Regards

wsw70
Communicator

Thank you very much (I actually cat'ed the ones which were copied by mistake to a new one and that new one got immediately indexed).

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...