Getting Data In

Universal Forwarder to different index server ports

fuster_j
Path Finder

Hi,

Is there any advantage to setup up Universal Forwarder to communicate different ports with index servers with load balancing instead all go to port 9997?

[tcpout]

autoLB = true

autoLBFrequency = 10

compressed = false

defaultGroup = AA

[tcpout:AA]

server = a1-abc.com:9995,b1.abc.com:9996,c1.abc.com:9997

Tags (1)
0 Karma

fuster_j
Path Finder

I'm think that each TCP session will have its own send/receive buffers. My real question is will they communicate concurrently in the load balancing mode?

0 Karma

Ayn
Legend

None at all that I can think of. Did you have an idea yourself, since you asked?

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...