Getting Data In

Manual sourcetype for data input not persistent when indexed

benwu63
Explorer

I configured a data input to monitor a directory holding the csv files that will be consumed by Splunk. I manually specify 'csv' as the sourcetype in inputs.conf. However, when those csv files being indexed by Splunk, those events appearing in the app context as "csv-1" as sourcetype and some later added csv files being indexed as "csv-2" as sourcetype.

From Splunk documentation (http://docs.splunk.com/Documentation/Splunk/latest/Data/Whysourcetypesmatter#How_Splunk_assigns_sour...), it indicated that explicit sourcetype specification will be used and it stops here. But why this is not the case for my data inputs???

Thanks in advance for your time in reading my question!

Tags (2)
1 Solution

Ayn
Legend

This is an effect of using the specific sourcetype "csv". See more info in this answer for instance: http://splunk-base.splunk.com/answers/72860/sourcetypes-keep-on-multiplying

View solution in original post

Ayn
Legend

This is an effect of using the specific sourcetype "csv". See more info in this answer for instance: http://splunk-base.splunk.com/answers/72860/sourcetypes-keep-on-multiplying

kristian_kolb
Ultra Champion

It's (still) a known bug. See the release notes.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...