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
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...