Getting Data In

Why is indexed extraction not happening when the data comes via the UF?

koshyk
Super Champion

Hi,

We have a quite a "piggy backed" data coming from a system and extracting as

[mysourcetype]
SHOULD_LINEMERGE=false
INDEXED_EXTRACTIONS=CSV
FIELD_NAMES=Date,Time,EmployeeID,EmployeeName
TIMESTAMP_FIELDS=Date,Time

(A) System Data collected using UF => (B) Sent to Heavy Forwarder => (C) HF to Indexer => (D) Clustered SH

We have the

  • inputs.conf in (A)
  • props.conf with INDEXED_EXTRACTIONS=CSV in (B) , (C) & (D)

Directly indexing the file works perfectly in standalone Splunk Instance.
But when the data comes via the UF, the indexed extraction is not happening.

Any reasons for this? Should we add props.conf to UF?

0 Karma
1 Solution

marthodder
Explorer

You're correct - You will need to add INDEXED_EXTRACTIONS=CSV in a props.conf for local deployment to each of the hosts.

[sourcetype] 
INDEXED_EXTRACTIONS=CSV

View solution in original post

marthodder
Explorer

You're correct - You will need to add INDEXED_EXTRACTIONS=CSV in a props.conf for local deployment to each of the hosts.

[sourcetype] 
INDEXED_EXTRACTIONS=CSV

koshyk
Super Champion

thanks for the tip.
UF also requires the props.conf

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!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

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