Getting Data In

Can the Cluster Master Also Do Indexer Discovery in the outputs.conf

dstuder
Communicator

I've got my universal forwarders and heavy forwarders doing indexer discovery through the cluster master like so ...

 

**************************
*      outputs.conf      *
**************************

[indexer_discovery:clustermaster]
pass4SymmKey = {password}
master_uri = https://{my cluster master}.domain.foo:8089

[tcpout:clustermastergroup]
indexerDiscovery = clustermaster
useACK = true

[tcpout]
defaultGroup = clustermastergroup

 

Is there any reason I could not do the same in the cluster master's outputs.conf file? Basically, it would ask itself over 8098 who the peer nodes are.

Labels (2)
1 Solution

isoutamo
SplunkTrust
SplunkTrust

if you are using it for clients then you should use it also for CM. 

View solution in original post

isoutamo
SplunkTrust
SplunkTrust

if you are using it for clients then you should use it also for CM. 

dstuder
Communicator

I did apply the outputs.conf config to the cluster master and indeed it did work just fine.

a_kearney
Path Finder

For the master_uri configuration did you use the same value as for the Forwarders or did you use the loopback interface address  (e.g. https://127.0.0.1:8089)?

 

0 Karma

dstuder
Communicator

I used the DNS entry for simplicity sake so that all the machines are set up the same way.

isoutamo
SplunkTrust
SplunkTrust
My personal advice is: use always dns names, never ips. That way it’s much easier to do changes later on.
0 Karma
Get Updates on the Splunk Community!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...