Deployment Architecture

Creating multiple indexes

louieb3
Path Finder

I just wanted to check to see how everyone goes about creating indexes. Right now, we seem to be creating a new index for each source that we ingest into splunk. So my question is - are we going about this wrong? Should we be putting more data in main? What are the pros and cons of creating separate indexes vs putting everything together in fewer indexes?

Tags (2)
0 Karma
1 Solution

lukejadamec
Super Champion

If you don't specify an index, then it can increase search time.

If you specify an index, it will reduce search time.

Splunk does not care how many indexes you have, but you might if you cannot easily specify the index that contains the data you're looking for.

View solution in original post

0 Karma

lukejadamec
Super Champion

If you don't specify an index, then it can increase search time.

If you specify an index, it will reduce search time.

Splunk does not care how many indexes you have, but you might if you cannot easily specify the index that contains the data you're looking for.

0 Karma

yannK
Splunk Employee
Splunk Employee

Thousands of indexes is overkill 🙂
from a couple to a dozen of indexes is a good start. all depends of your volume.

Having several indexes is useful for :

  • access control, with permissions role/index
  • retention, to have different size/time retentions per index
  • search performances, by searching on a specific index
Get Updates on the Splunk Community!

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...