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.

Sign up for GitHub

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

Jump to bottom

Geth node synchronization monitoring #3145

Closed
nkuba opened this issue Aug 9, 2022 · 1 comment
Closed

Geth node synchronization monitoring #3145

nkuba opened this issue Aug 9, 2022 · 1 comment
Labels
☁️ infrastructure

Comments

@nkuba
Copy link
Member

nkuba commented Aug 9, 2022

This issue is a continuation of #3012

We should monitor our geth instance synchronization with the chain. First, we should verify if the metrics exposed by the geth client suit our needs.

Another solution could be comparing the latest block (ethereum_latest_block_number) with the latest block numbers returned from public APIs like Alchemy, Infura, or Etherscan.
@nkuba nkuba mentioned this issue Aug 9, 2022
Closed
34 tasks
@electropolis electropolis mentioned this issue Sep 14, 2022
Closed
@pdyraga pdyraga added this to the v2.0.0-m2 milestone Oct 3, 2022
@pdyraga
Copy link
Member

pdyraga commented Oct 4, 2022

Let's stick to external providers for now. To run our own Goerli node after the merge, we'd have to set up Prysm as well.

@pdyraga pdyraga closed this as completed Oct 4, 2022
@pdyraga pdyraga removed this from the v2.0.0-m3 milestone Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
☁️ infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pdyraga @nkuba