feat(metrics): add Prometheus metrics support for beacon client - #1527
Draft
tosynthegeek wants to merge 3 commits into
Draft
feat(metrics): add Prometheus metrics support for beacon client#1527tosynthegeek wants to merge 3 commits into
tosynthegeek wants to merge 3 commits into
Conversation
* Implement core beacon metrics (head slot, epochs, active validators, reorgs, deposits) * Expose configurable metrics address and port in the beacon node CLI * Integrate with Grafana dashboard via `beaconMetrics.json` * Update ream_launcher.star + Kurtosis integration Closes ReamLabs#1526
tosynthegeek
requested review from
Kayden-ML,
KolbyML and
shariqnaiyer
as code owners
July 18, 2026 21:26
tosynthegeek
marked this pull request as draft
July 18, 2026 21:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong?
The beacon node had no Prometheus metrics,
ream-metricswas wired into the lean client only,BeaconNodeConfighad no metrics flag, and there was no way to expose a /metrics endpoint. This blocked Kurtosis integration, since theethereum-packageconfig wires every CL participant's metrics port into a shared Prometheus/Grafana stack via Dora. See #1526.How was it fixed?
Added a Prometheus metrics HTTP endpoint to the beacon node, with configurable address/port exposed via CLI flags.
Added beacon metrics into the beacon node's fork choice, gossipsub validation, engine API, networking, and KZG/DAS paths, implementing the beacon-metrics interop spec plus the PeerDAS gossip-verification, KZG-batch, reconstruction, and Fulu
engine_getBlobsV2/V3metrics.Added
beaconMetrics.json, a Grafana dashboard covering all wired metrics.Some metrics have been added but not wired as there areno underlying implementation to hook into yet.
beacon_custody_groups_backfilled,beacon_partial_message_*,beacon_useful_full_columns_received_total,beacon_fast_confirmation_*To-Do