Getting Data In

INDEXED_EXTRACTIONS, Universal Forwarder & Splunk Cloud

zapping575
Communicator

One of my sourcetypes is a CSV file (with CSV header)

I was using this sourcetype stanza in props.conf:

[foo_bar]
INDEXED_EXTRACTIONS = csv
TIME_FORMAT = %Y%m%d%H%M%S%Q
TIMESTAMP_FIELDS = Year,Month,Day,Hour,Minute,Second,Seq
HEADER_FIELD_LINE_NUMBER = 1
HEADER_FIELD_DELIMITER = ;
FIELD_DELIMITER = ;
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
REPORT-foo_bar-default = sourcefields-default

I have come to notice that with splunk cloud, the indexed extractions are apparently no longer being applied. While the sourcetype is correctly assigned and the REPORT is also being applied, the actual indexed extraction does not take place.  When I run a search for sourcetype foo_bar, I cannot see any of the fields defined by the CSV header. I also made sure the CSV header is actually present.

My setup is like this:

(1) Universal Forwarder -> (2) Universal ("Intermediate") Forwarder -> (3) Splunk Cloud

I tried applying these settings at both (1) and (3). In both cases it did not work.

Am I missing out on something?

Labels (4)
0 Karma
1 Solution

zapping575
Communicator

Rather unsurprisingly, this was another case of PEBKAC.

Changing the value of

HEADER_FIELD_LINE_NUMBER

back to 0 did the trick.

props.conf on the UF:

[source:://my.csv]
INDEXED_EXTRACTIONS = csv
TIME_FORMAT = %Y%m%d%H%M%S%Q
TIMESTAMP_FIELDS = Year,Month,Day,Hour,Minute,Second,Seq
HEADER_FIELD_LINE_NUMBER = 0
HEADER_FIELD_DELIMITER = ;
FIELD_DELIMITER = ;
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
sourcetype = foo_bar

props.conf on my local stand alone instance:

[foo_bar]
REPORT-foo_bar-default = sourcefields-default

View solution in original post

0 Karma

zapping575
Communicator

Rather unsurprisingly, this was another case of PEBKAC.

Changing the value of

HEADER_FIELD_LINE_NUMBER

back to 0 did the trick.

props.conf on the UF:

[source:://my.csv]
INDEXED_EXTRACTIONS = csv
TIME_FORMAT = %Y%m%d%H%M%S%Q
TIMESTAMP_FIELDS = Year,Month,Day,Hour,Minute,Second,Seq
HEADER_FIELD_LINE_NUMBER = 0
HEADER_FIELD_DELIMITER = ;
FIELD_DELIMITER = ;
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
sourcetype = foo_bar

props.conf on my local stand alone instance:

[foo_bar]
REPORT-foo_bar-default = sourcefields-default
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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...