lambdaclass / lambdaclass/lambda_ethereum_consensus
Add cache metrics
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Having hit/miss metrics of Blocks might be useful
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.
Research direction
Locate the Blocks cache implementation and review any existing metrics or observability entry points. Determine how cache hits and misses should be counted and exposed, then verify that both outcomes are reported consistently in the relevant tests or checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100