Splunk Search

Splunk distributed search between two datacenters

imacdonald2
Path Finder

We have two datacenters, Production and QE, each datacenter has a completely seperate AD infrastructure. Our main splunk indexer machine is in our production datacenter. We are running splunk 4.

QE needs access to just a couple indexes on for our production servers.

Am I crazy, will this work?

Set up a search head server that lives in the QE Data center and authenticates users using QE AD domain, it does nothing other than send queries to the main indexer, the main indexer authenticates to using the production AD servers which are completely seperate from the QE ones.

I read in one of the answers on here that in V4 the search head is responsible for all the authentication and authorization and the indexer just trusts that it has been set up correctly, can someone confirm this, if so then it appears my idea will work.

Tags (2)
1 Solution

dskillman
Splunk Employee
Splunk Employee

You are correct. The Search Head controls auth for the search.

View solution in original post

jensfresson
New Member

What are the requirements regarding network connections between 2 datacenters. Speed, replications etc.
Index clusters between datacenters?
Index servers in only 1 datacenter receiving data from other datacenters. What network performance does that require if you still want to be able to see data "real-time"?

Is there a best practice for this?

0 Karma

dskillman
Splunk Employee
Splunk Employee

You are correct. The Search Head controls auth for the search.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...