Getting Data In
Highlighted

Splunk Indexer as Virtual Machine - Best practices?

SplunkTrust
SplunkTrust

Has anybody implemented a distributed Splunk Environment using Virtual Machines from top to bottom?

This seems to be hardly an issue for most of the components, but the Indexer seems to generate the most worry. Are there any resources outlining any unique configuration that would make a virtual Indexer perform better?

Highlighted

Re: Splunk Indexer as Virtual Machine - Best practices?

Engager
Highlighted

Re: Splunk Indexer as Virtual Machine - Best practices?

Path Finder

We started off with our indexers as VM's. It worked OK in the beginning, as we moved on it turned into a bottle neck. So we ended up buying hardware for the indexers. Our search heads run fine on a VM.

0 Karma
Highlighted

Re: Splunk Indexer as Virtual Machine - Best practices?

Builder
0 Karma
Highlighted

Re: Splunk Indexer as Virtual Machine - Best practices?

Splunk Employee
Splunk Employee

Most critical aspects of a successful VM deployment:
- vCPU reservation of at least 8 cores, 12 is better
- vRAM reservation of at least 12GB
- eager-zero provisioned disk providing at least 800IOPS concurrently per indexer

As long as you don't oversubscribe and configure following the recommendations in the TechBrief, an indexer can work well in a virtual environment. Did I mention resource reservations?

If your VM hosts are oversubscribed, you don't reserve resources and you are ending up with high CPU Ready counts; or if your underlying disk is not performing at the recommended rates, things will probably not live up to your expectations.