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!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...