All Apps and Add-ons

Scaling the VMWare Forwarder Appliance

beaunewcomb
Communicator

Has anyone mastered the art of scaling the Forwarding Appliance for the VMWare app? Say I want to put 100 hosts on one appliance and have sufficient CPU\MEM\DISK resources. Has anyone worked through the requirements and accomplished this reliably in production? I'm looking for some sort of chart which gives a rough idea of the resources required to accommodate x number of ESX hosts.

1 Solution

sfjim
Engager

I think you'll be better off splitting up the hosts between multiple FAs. Scale out, not up.

It adds the benefit of easier scheduling of the FA VMs on your hypervisor.

The documentation suggests 20-30 hosts per 4 vCPU FA. I suspect the limit is more centered around the number of VMs on those hosts and you want to keep it under 300 VMs per FA.

View solution in original post

sfjim
Engager

I think you'll be better off splitting up the hosts between multiple FAs. Scale out, not up.

It adds the benefit of easier scheduling of the FA VMs on your hypervisor.

The documentation suggests 20-30 hosts per 4 vCPU FA. I suspect the limit is more centered around the number of VMs on those hosts and you want to keep it under 300 VMs per FA.

Get Updates on the Splunk Community!

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...

Detecting Remote Code Executions With the Splunk Threat Research Team

REGISTER NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If ...