Deployment Architecture

Updating Splunk Index Group information in indexer servers for cluster setup.

ramanapvr
New Member

Hi Team,

1) We have a cluster setup with two indexers getting data from at least 50+ forwarder servers (i.e. Linux and Windows)
2) For this, we need to define the INDEX GROUP with tcpout and indexers information in outputs.conf. Below is the example of one indexing group. Like the example mentioned below
[tcpout:project_ABCD]
Disabled = false
Server = 192.168.X.X:1234,192.168.X.X:5678.

Is it possible to define Project index group(i.e. tcpout) and indexers information in indexers server peers only.

This is to avoid manual intervention on the forwarders side (i.e. editing outputs.conf file) and also is it advisable to use it on the indexer server side because of multiple indexing groups.

Regards,
Peri

Tags (1)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Defining forwarder configuration in one single place and sending it out to the forwarders in case of updates without manual intervention on the forwarders matches Splunk's Deployment Server perfectly, see http://docs.splunk.com/Documentation/Splunk/6.0.2/Updating/Aboutdeploymentserver for reference.

0 Karma
.conf21 Now Fully Virtual!
Register for FREE Today!

We've made .conf21 totally virtual and totally FREE! Our completely online experience will run from 10/19 through 10/20 with some additional events, too!