Getting Data In

props.conf extractions

gnovak
Builder

I have a quick question here. I have a distributed environment with about 5 indexers and then a main search head.

I have a props.conf file on 1 of the indexers and it's being used to extract data into fields. However when searching on the main search head for this data, the fields aren't present. If I search on the indexer itself where the props.conf resides, the fields are present.

Do I have to put the extractions in the props.conf on the search head as well? I would have thought putting it on the indexer was the right thing to do and that this would filter down when searching on the main search head.

Tags (1)
0 Karma
1 Solution

gnovak
Builder

Actually nevermind! I put the extractions in the props.conf also on the search head and this resolved the issue. No worries here!

View solution in original post

gnovak
Builder

Actually nevermind! I put the extractions in the props.conf also on the search head and this resolved the issue. No worries here!

Jon_Webster
Splunk Employee
Splunk Employee

If you think about it, since Splunk does the field extractions at search time, and the search head has to coordinate and post-process the data coming from all the indexers, the search head must have all search-time knowledge objects.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...