Getting Data In

Can splunk read logs in CSV format?

balbano
Contributor

Hi, we are currently testing a Palo Alto app sec firewall and are sending some test logs over to the central indexer in CSV format. Can splunk read CSV files?

The splunkd.log file is giving me somewhat of an error stating the following:

05-25-2010 14:21:33.678 ERROR TailingProcessor - Ignoring path due to: File will not be read, is too small to match seekptr checksum (file=PATHTOMYFILES). Last time we saw this initcrc, filename was different. You may wish to use a CRC salt on this source. Consult the documentation or contact Splunk Support for more info.

Let me know. Thanks!

Brian

Tags (2)
0 Karma
1 Solution

Nicholas_Key
Splunk Employee
Splunk Employee

sure. please test if it works with

crcSalt = <SOURCE>

in the particular stanza of your app's inputs.conf

View solution in original post

balbano
Contributor

Doesn't look like it worked. Here is my stanza:

[monitor:///pathtomyfiles]
disabled = false
host =
host_segment = 3
index = myindex
sourcetype = mysourcetype
crcSalt = /pathtomyfiles

Is this correct syntax? not seeing the error message anymore but it still doesn't look like the files are being indexed.

Brian

0 Karma

balbano
Contributor

and Lowell since this was a test sample of csv logs the impact was not great but in the future I will definitely keep that in mind!!! Thanks again!!!

0 Karma

balbano
Contributor

sweet... that worked!!!!!!!!! Thanks GUYS!!!!!

0 Karma

Lowell
Super Champion

Also, keep in mind that anytime you change crcSalt you are likely to re-index all your files. You should also be aware that setting crcSalt = <SOURCE> means that if you rotate your log files they may be indexed again. Normally splunk detects and handles this automatically, but using <SOURCE> will effectively disable this feature. So you may need to update your rotation scheme to move log files to a different folder, or make sure your monitor is only looking at your non-rotated files. Just a heads up.

Lowell
Super Champion

No, you want the literal value "<SOURCE>". That is a special value with a special meaning. Take a look at http://www.splunk.com/base/Documentation/4.1.2/Admin/Inputsconf

Nicholas_Key
Splunk Employee
Splunk Employee

sure. please test if it works with

crcSalt = <SOURCE>

in the particular stanza of your app's inputs.conf

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!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...