Knowledge Management

Setting props.conf on the search head or cluster master

mah
Builder

Hi, 

I want to know what is the difference between setting props.conf on the search head instead or on the cluster master in a distributed environment. (1 Search head, 1 CM, 2 IDX for example)

I have to set an field extraction from custom logs, and so set EXTRACT-fields parameter in a props.conf with the corresponding regex and I was wondering this above question.

If someone can help me to understand, it will be nice. 

Thanks.

 

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

Desired location of props.conf depends on the effect you want to achieve. If you want search-time extractions, you need props.conf and transforms.conf on search-heads (either put there directly or distributed from the deployer). If you want indexed field extraction, you need to put the files on the server(s) in the ingest path (indexers and/or heavy forwarders).

There would be no point in defining search-time extraction on indexers as there is no point of defining ingest time indexed field extractions on search heads.

Of course you can make "common" props.conf and transforms.conf containing both types of configurations and put them on both layers of your environment. This way only settings relevant to the appropriate layer would be in effect, the rest of the settings would be ignored.

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!

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 ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...