Deployment Architecture

Distributed search from a SH Cluster to multiple Indexer Clusters

Aatom
Explorer

Hey Splunkers!

We have multiple IDX/SH clusters that are peered based on regulatory/compliance/operational reasons. We have a specific SHC that we would like to de-peer from an older IDX cluster. Indexes are reused and migrated across different IDX clusters frequently.

What is the fastest and most accurate way to see what data is being fetched from the IDX clusters by a SHC?

Thanks in Advance!

Labels (1)
0 Karma

burwell
SplunkTrust
SplunkTrust

Hi.  Just by searching answers I found these two: You can list the indexers your heads are talking to with

| rest /services/server/info | table splunk_server

 You can list all the indexes with tstats (you would need a large window of time, possibly)

| tstats count WHERE index=* by index | table index

 

0 Karma

Aatom
Explorer

Thanks @burwell , we know we are currently peered, and am familiar with both the options you provided, but I am trying to go deeper. What I would like to find is an output that shows actual results (bytes, buckets, meta, etc) returned from the Indexer Cluster we want to de-peer from, based on the outgoing queries from the SHC.

0 Karma

burwell
SplunkTrust
SplunkTrust

You want to know when your users are querying the indexers you want to de peer from?

0 Karma
Get Updates on the Splunk Community!

Exciting News: The AppDynamics Community Joins Splunk!

Hello Splunkers,   I’d like to introduce myself—I’m Ryan, the former AppDynamics Community Manager, and I’m ...

The All New Performance Insights for Splunk

Splunk gives you amazing tools to analyze system data and make business-critical decisions, react to issues, ...

Good Sourcetype Naming

When it comes to getting data in, one of the earliest decisions made is what to use as a sourcetype. Often, ...