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

Round Robin based loadbalancing support #177

Closed
pankaj-k opened this issue Mar 31, 2021 · 2 comments
Closed

Round Robin based loadbalancing support #177

pankaj-k opened this issue Mar 31, 2021 · 2 comments

Comments

@pankaj-k
Copy link

It will be nice if we could provide a comma or colon seperated url's in the requestUri. If the sink can do a round robin based load balancing between the two URI's that will be awesome. If it is already possible then please let me know.

{
  "Serilog": {
    "Using": [ "Serilog.Sinks.Http" ],
    "MinimumLevel": "Verbose",
    "WriteTo": [
      {
        "Name": "Http",
        "Args": {
          "requestUri": "http://serverone:9900;http://servertwo:9901"
          "loadBalance" : "true"
        }
      }
    ]
  }
}

The Elasticsearch Sink does that to some extent.
Quoting what the person said:
That is correct. The ES sink uses the connection pool functionality. So normally you pass in a couple of endpoints and the client is clever enough to check health and connect to the available one.

@github-actions
Copy link
Contributor

Hi there and welcome to this repository!

A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it.

@FantasticFiasco
Copy link
Owner

Hi!

This falls into the same ballpark as #134 and #157. It's a network problem that easily can be solved at the network level. There already exists solutions for this, and because of that I'm closing this issue.

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

2 participants