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

[proxyd] support different BackendOptions for different backends within the same config #211

Open
hmvien opened this issue Mar 3, 2025 · 0 comments

Comments

@hmvien
Copy link

hmvien commented Mar 3, 2025

Is your feature request related to a problem? Please describe.
We have a proxyd instance with several RPC backends configured with different level of reliability. As a result, we would like to configure different max_latency_threshold and max_error_rate_threshold per backend. The current state is that proxyd accepts a single block for BackendOptions and it will be applied to all backends. We would like more control.

Describe the solution you'd like
A tier-based config parsing logic that will allow the max_latency_threshold and max_error_rate_threshold to take precedence within the backends config block. If this value is not set, then it will fallback to use the backend options

It might be worthwhile to apply this logic to all existing configs in the BackendOptions block.

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

1 participant