[FEATURE] add metric which exposes number of headers/data which did not validate successfully
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability-sre
Research direction
Start by locating the existing data-availability validation metrics and retry handling in the Go project. Confirm how headers and data are distinguished, then verify that a metric labeled with chain_id and type reports validation failures only after all retry attempts are exhausted.
Written by the indexing model from the issue text.
Description
add a metric
da_submission_failed{chain_id="collect-testnet-1",type="header"} 3
or equivalent that tracks the number of times da validation failed all retry attempts.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 evstack/ev-metrics
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
evstack/ev-metrics#23 ·
All issues in evstack/ev-metrics
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
alexgorbatchev/dotfiles#107 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100