Getting Data In

Why is Splunk not capturing new content in a CSV file input and indexing it?

bosch_softtec
Path Finder

Hi,

Splunk 6.5.0

I have the scenario that I have to import every hour a csv (File A) file from a system which has no network access/connection to the Splunk environment. I've created a csv (File B) file on the Splunk indexer which is defined as data input.

Every hour there is running a process which cuts the contend from File A and writes it to File B. Mostly Splunk is indexing the content but sometimes it happens, that File B is filled with the new content but Splunk doesn't index it.

Has somebody an idea why that happens?

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Does the file have a large header that is the same in every instance? Splunk will look at the first 256 bytes to determine if it's already indexed the file and refuse to ingest it again. Consider changing the crcSalt or initCrcLength settings in inputs.conf.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Does the file have a large header that is the same in every instance? Splunk will look at the first 256 bytes to determine if it's already indexed the file and refuse to ingest it again. Consider changing the crcSalt or initCrcLength settings in inputs.conf.

---
If this reply helps you, Karma would be appreciated.

bosch_softtec
Path Finder

Hi, it could happen that there is no change in the header or first 256 bytes.
Regarding your hint, i'll change the size of the initCrcLength to a higher value and check if my problem has gone.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...