Splunk Enterprise

Are there any additional storage or performance considerations before pursuing overhead with splitting indexes?

bsouers
New Member

We currently have a multi-tier Splunk Enterprise instance with search-head clustering and indexer clustering.

All of our data comes in from Universal Forwarders on remote VMs (thousands of them) from different customers.

Our inputs.conf on all of the forwarders are set to send to only a couple of indexes in our indexer cluster.

 

We are planning a project to split these indexes on a per-customer basis.

For example, index "main" would become "main-cust1", "main-cust2", etc.

 

The point behind this is to allow RBAC on a per-customer basis (by limited access to customer specific indexes).

 

Are there any additional storage or performance considerations that should be evaluated before pursuing this change?

Labels (2)
0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...