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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...