Deployment Architecture

Distributed search sizing

ontai
Explorer

I've looked through some of the documentation for separating search heads from indexers depending on the number of concurrent searches and users. I'm wondering what a rough idea of the architecture and hardware requirements would look like to support:

10-20 GB per day
20 concurrent users
10 concurrent saved searches

Thanks.

Craig

Tags (1)
0 Karma

araitz
Splunk Employee
Splunk Employee

Given your user and scheduler concurrency, you would probably be best off implementing an indexer and a search head. Although you can easily index 80-100 GB/day on a single commodity server, having 20 concurrent users and 10+ concurrent scheduled searches on the same machine wouldn't allow for the best user experience or much room for growth.

0 Karma

Takajian
Builder

I agree your suggestion. This is appropriate sizing with considering to future plan. My answer was rough idea.

0 Karma

Takajian
Builder

I do not think you do not need dedicated search head when you index data less than 100GB per day on one box server. You can also refer to following site. Hope this help.

http://docs.splunk.com/Documentation/Splunk/latest/installation/capacityplanningforalargersplunkdepl...

0 Karma
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...