Getting Data In

Splunk indexes.conf by deployment server

lmjoin
Explorer

I have installed search head cluster and want pushing configuration by deployment server . But unable to find how to make and push indexes.conf to all indexers ( not in clustering ) . Thanks for reply in advance

Labels (1)
Tags (1)
0 Karma
1 Solution

woodcock
Esteemed Legend

You need to create an app with a deploymentclient.conf that points to the Deployment Server. Then create another app with a indexes.conf in it. Then create $SPLUNK_HOME/etc/system/local/serverclass.conf with a serverclass entry that has a whitelist that matches all of your indexers and that contains both the apps that you created.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

Apply shcluster-bundle applies a bundle to your searchhead cluster. Read the deployment server docs linked to earlier.

0 Karma

lmjoin
Explorer

i have what to add in serverclass.conf for indexers but unable to make to find location where i put indexes.conf for

ALL
INDEXERS
[serverClass:all_indexer]

whitelist.0

Hostname

whitelist.1

Hostname

whitelist.2

Hostname

whitelist.3

Hostname

whitelist.4

Hostname

restartSplunkd

true
[serverClass:all_indexer:app:ito_det_deploymentclient]
[serverClass:all_indexer:app:ito_det_indexer_base]
[serverClass:all_indexer:app:ito_det_indexes]
[serverClass:all_indexer:app:ito_det_license_slave]
[serverClass:all_indexer:app:ito_det_dbx_timezone]
[serverClass:all_indexer:app:Splunk_TA_nix]
[serverClass:all_indexer:app:TA-­‐sos]

0 Karma

lmjoin
Explorer

ALL
INDEXERS
[serverClass:all_indexer]

whitelist.0

HN

whitelist.1

HN

whitelist.2

HN

whitelist.3

ALPD835.aldc.att.com

whitelist.4

ALPD836.aldc.att.com

restartSplunkd

true
[serverClass:all_indexer:app:ito_det_deploymentclient]
[serverClass:all_indexer:app:ito_det_indexer_base]
[serverClass:all_indexer:app:ito_det_indexes]
[serverClass:all_indexer:app:ito_det_license_slave]
[serverClass:all_indexer:app:ito_det_dbx_timezone]
[serverClass:all_indexer:app:Splunk_TA_nix]
[serverClass:all_indexer:app:TA-­‐sos]

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Best practice would be to turn your indexers into an indexer cluster, and then push configuration to your indexers from the cluster master.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

If you're certain you need indexers as deployment clients (hint: you don't, you want a cluster) then you can turn on their deployment client the same way you turn it on for forwarders: via the CLI splunk set deploy-poll host:port or via deploymentclient.conf

lmjoin
Explorer

thanks for reply , how to do entry in which file for same

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You can configure indexers to be deployment clients of your deployment server, but that's kinda what the cluster master is there for. For example, the cluster master will trigger a rolling restart when new configuration requires a restart - some indexers will always be there. The deployment server will cause all indexers to restart, possibly at the same time.

Who says you need to configure your indexers by deployment server? Ask them why you're not allowed to use best practices, and if they'll take responsibility when the entire indexing tier is down at the same time after a small configuration change.

0 Karma

lmjoin
Explorer

We need to do here by deployment server

0 Karma

lmjoin
Explorer

That is true , here we need such configuration.

0 Karma
Get Updates on the Splunk Community!

Buttercup Games Tutorial Extension - part 9

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Buttercup Games Tutorial Extension - part 8

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Introducing the Splunk Developer Program!

Hey Splunk community! We are excited to announce that Splunk is launching the Splunk Developer Program in ...