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
Get Updates on the Splunk Community!

Stay Connected: Your Guide to February Tech Talks, Office Hours, and Webinars!

💌 Keep the new year’s momentum going with our February lineup of Community Office Hours, Tech Talks, ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Incident Response: Reduce Incident Recurrence with Automated Ticket Creation

Culture extends beyond work experience and coffee roast preferences on software engineering teams. Team ...