You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: