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!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...