Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation conflict regarding load balancers #2358

Open
splaarmy opened this issue Feb 28, 2024 · 2 comments
Open

Documentation conflict regarding load balancers #2358

splaarmy opened this issue Feb 28, 2024 · 2 comments
Assignees

Comments

@splaarmy
Copy link

Describe the bug
SC4S documentation mentions not using load-balancers in a few places, such as https://splunk.github.io/splunk-connect-for-syslog/main/lb/, however on the page linked below seems to list a load-balancer as a prerequisite:

A network load balancer (NLB) configured for round-robin. Note: Special consideration may be required when more advanced products are used. The optimal configuration of the load balancer will round-robin each http POST request (not each connection).

https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/getting-started-runtime-configuration/

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/getting-started-runtime-configuration
  2. Item in question is currently the second paragraph in the Prerequisite section.
@fyodorr
Copy link

fyodorr commented Mar 22, 2024

The loadbalancers in this case have different usages.

The loadbalancer that's recommended is the load balancer for balancing the http (HEC) traffic to indexers.

The loadbalancer that's not recommended is the load balancer that's placed infront of the syslog server (SC4S).

@rjha-splunk
Copy link
Collaborator

We are working on documentation , we will update the sections to make it more clear cc: @mstopa-splunk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants