Getting Data In

Why is a props.conf change on a universal forwarder not being applied in a multisite Splunk 6.2.0 indexer clustering environment?

afmohamm
Engager

I have a Splunk 6.2.0 multisite cluster setup. Per site, there is one indexer, one search head and a master. I am pulling logs from a client on Windows using splunk universal forwarder, but I need to change the Line Break. I have defined a new sourcetype in props.conf and placed it on the client and restarted the splunkd on the client. I still don't see the changes when I search the data on the search head.

Do I have to define the sourcetype on the indexer as well? or just the indexer and not in the client?

Thanks

0 Karma
1 Solution

gfuente
Motivator

Hello

The parsing stage happens in the indexers (or Heavy Forwarders) not in the Universal Forwarder

So that props must be placed in the indexers, in your case as you are using a cluster, then you need to deploy it through the cluster master, using master apps, and the apply cluster bundle command

Regards

View solution in original post

gfuente
Motivator

Hello

The parsing stage happens in the indexers (or Heavy Forwarders) not in the Universal Forwarder

So that props must be placed in the indexers, in your case as you are using a cluster, then you need to deploy it through the cluster master, using master apps, and the apply cluster bundle command

Regards

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...