Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Head metrics are initialized to 0 when data exists in DB

Open
#550 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
blockchain, observability

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.

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:

Image Notice the purple spike at the right of the first two graphs
Dominant language
Rust
Stars
82
Forks
28
Avg merge
1d 20h
Merged PRs (30d)
20

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.