Dashboards & Visualizations

Load balancing HEC input, Deployment Server and token assignment

_smp_
Builder

I have three Heavy Forwarders managed by a Deployment Server and I want to use it to deliver a package containing an HTTP Event Collector input. I want the incoming HTTP data to be load-balanced to the Heavy Forwarders by a hardware load-balancer. Is it OK to deploy one HEC input with the same token value to three Heavy Forwarders? Are there any risks or technical limitations around doing this, or is this the right way to do it?

0 Karma

manjunathmeti
Champion

If data is sent to the heavy forwarders by a load balancer then you should have same HEC input with the same token value on all Heavy Forwarders. So, It is OK to deploy one HEC input with the same token value to all three Heavy Forwarders.

0 Karma

dkeck
Influencer

Hi,

there are some docs on this topic

http://dev.splunk.com/view/event-collector/SP-CAAAE73 this might help.

0 Karma

dkeck
Influencer

Did it help you? If it was helpfull please accept the answer, thank you

0 Karma

gabrielbico
New Member

This link it is not valid anymore...

0 Karma
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!

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...