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

[exporter/splunkhec] Reconnect on 502/429 errors #18281

Closed
atoulme opened this issue Feb 3, 2023 · 0 comments
Closed

[exporter/splunkhec] Reconnect on 502/429 errors #18281

atoulme opened this issue Feb 3, 2023 · 0 comments
Labels

Comments

@atoulme
Copy link
Contributor

atoulme commented Feb 3, 2023

Component(s)

exporter/splunkhec

Is your feature request related to a problem? Please describe.

When the exporter receives a 502 or 429 from a load balancer or cluster, it keeps using the same HTTP connection and may hit the same node as load balancers may use connection-based load balancing rather than per request.

Describe the solution you'd like

The exporter should have the option to disconnect and reconnect to the endpoint by closing explicitly the HTTP connection on any non successful status code, so that the load balancer can rebalance HTTP connections.

Describe alternatives you've considered

No response

Additional context

No response

@atoulme atoulme added enhancement New feature or request needs triage New item requiring triage exporter/splunkhec priority:p2 Medium and removed needs triage New item requiring triage labels Feb 3, 2023
@atoulme atoulme closed this as completed Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant