Diag should include write counters
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Especially config CB
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.
Research direction
The issue names diagnostic output and config CB but no files, tests, or specific counters. First locate the diagnostic entry point and the config CB implementation, then clarify which write counters are required and where they should appear; done means those counters are exposed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100