lambdaclass / lambdaclass/ethlambda
Head metrics are initialized to 0 when data exists in DB
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
When starting a node with data in its DB, we initialize the head slot, justified slot, and finalized slot to 0, when they could be using the data we have in our DB. This can cause weird spikes in Grafana, since the head is updated more frequently than the others:
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
Start by locating the node-startup path that initializes the head, justified, and finalized slots, then trace how persisted data is read from the DB and exposed to metrics. Confirm the existing data is used instead of zero values, and verify that startup metrics no longer show the reported Grafana spikes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100