Deployment Architecture

Using Heavy Forwarder as a Relay

dokaas_2
Communicator

I've seen the warnings of having UFs sending HFs and relaying to a index cluster. The objection seems to be around uneven distribution of events from the HFs to the indexers. However, doesn't setting the HFs outputs.conf variables: indexAndForward=false and autoLBFrequency=30 fix those issues?

Basically, have the UFs load balance to a pool of HFs and the pool of HFs load balance to the index cluster. If you do this, will you still have problems?

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust
Hi
Here is one presentation about event distribution. https://www.slideshare.net/Splunk/best-practices-for-splunk-deployments
I think that this explain that.
r. Ismo
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...