Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metrics exporter calls ancient /eth/v1/beacon/blocks/{block_id} api #116

Open
nflaig opened this issue Jan 30, 2025 · 1 comment
Open

Metrics exporter calls ancient /eth/v1/beacon/blocks/{block_id} api #116

nflaig opened this issue Jan 30, 2025 · 1 comment

Comments

@nflaig
Copy link

nflaig commented Jan 30, 2025

When running Kurtosis with the following setting

ethereum_metrics_exporter_enabled: true

I can see a lot of errors due to the exporter calling /eth/v1/beacon/blocks/{block_id}.

Jan-30 16:13:19.233[rest]             warn: Route GET:/eth/v1/beacon/blocks/finalized not found
Jan-30 16:13:19.236[rest]             warn: Route GET:/eth/v1/beacon/blocks/head not found
Jan-30 16:13:19.242[rest]             warn: Route GET:/eth/v1/beacon/blocks/finalized not found
Jan-30 16:13:19.244[rest]             warn: Route GET:/eth/v1/beacon/blocks/head not found
Jan-30 16:13:23.248[rest]             warn: Route GET:/eth/v1/beacon/blocks/0x9544f7f9...b6fd069dff not found

We have removed this api more than 6 months ago from Lodestar and it's not part of the latest beacon api spec release given those were removed almost 3 years ago ethereum/beacon-APIs#218 there.

I would be surprised if other clients still support this api, likely just nobody noticed these errors before but I know that all clients support getBlockV2 so it's probably best to start using that api instead.

@nflaig
Copy link
Author

nflaig commented Jan 30, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant