Getting Data In

About specification of "initCrcLength" option and "crcSalt" option.

  • About initCrcLength

I know that changing initCrcLength option cause reindex and ignoreOlderThan option is workaround.

But if target is the log updated frequently, how can I avoid reindex?
Also, If I change initCrcLength, previous crc information in fishbucket will be cleared?

  • About crcSalt

Does adding crcSalt option causes reindex?
Also does it clear previous crc information in fishbucket?

If someone knows about it, please tell me.

0 Karma


hi @yutaka1005 ,

You can go through this link. This might help you.

0 Karma


I am not sure that I understand your question. The functioning of crcSalt and initCrcLength are explained well in the docs. But what are you trying to archieve exactly?


0 Karma


Thank you for comment.

What I want to know is the following two points.

  • Is reindex occured if I set crcSalt = option?

  • The workaround for preventing reindex caused by changing initCrcLength is "ignoreOlderThan".
    But "ignoreOlderThan" option sees the update time of the file, so it will not be effective for files that are frequently updated.
    So I want to know method of reindex prevention caused by changing initCrcLength, when I monitoring frequently updated files.


Hi @yutaka1005 


You got the answer for your query?

If yes, can you please explain it?

0 Karma
Get Updates on the Splunk Community!

Dashboard Studio Challenge - Learn New Tricks, Showcase Your Skills, and Win Prizes!

Reimagine what you can do with your dashboards. Dashboard Studio is Splunk’s newest dashboard builder to ...

Introducing Edge Processor: Next Gen Data Transformation

We get it - not only can it take a lot of time, money and resources to get data into Splunk, but it also takes ...

Take the 2021 Splunk Career Survey for $50 in Amazon Cash

Help us learn about how Splunk has impacted your career by taking the 2021 Splunk Career Survey. Last year’s ...