Capture JSON-RPC error metrics
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability
Research direction
Start by tracing how bproxy currently records HTTP request failure metrics, then inspect where JSON-RPC response bodies are handled. The work is done when failure counts and rates can be aggregated by method and reason, with overly detailed error messages cleaned up as needed.
Written by the indexing model from the issue text.
Description
Currently bproxy captures http request failures but doesn't capture anything related to json-rpc errors. It would be nice to generate metrics that could tell us the counts and rates of failure reasons sliced by the method and reason.
This will require deserializing the response body and potentially cleaning up the error message if it's too detailed for aggregation.
- Dominant language
- Go
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flashbots/bproxy
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in flashbots/bproxy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·