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

NodeStatus API Endpoint for checking node health #5762

Closed
Kubuxu opened this issue Mar 10, 2021 · 2 comments · Fixed by #5767
Closed

NodeStatus API Endpoint for checking node health #5762

Kubuxu opened this issue Mar 10, 2021 · 2 comments · Fixed by #5767

Comments

@Kubuxu
Copy link
Contributor

Kubuxu commented Mar 10, 2021

Initially, it would be used to confirm that node is in a good state before producing a message.

Checks proposed:

  • the sync status: how far out of sync the node is.
    • Use the difference between the current time and genesis to figure out which epoch we should be at.
  • peering status: do we have more than 5 peers with positive pubsub scores?
    • i.e. are we confident that if we send this message now, it will be properly propagated to the network?
@Kubuxu Kubuxu added the team/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs label Mar 10, 2021
@vyzo vyzo self-assigned this Mar 10, 2021
@magik6k
Copy link
Contributor

magik6k commented Mar 10, 2021

Maybe also some chain health metric, based on something like the number of blocks in last X epochs vs the expected number

@vyzo vyzo mentioned this issue Mar 10, 2021
@raulk raulk removed the team/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs label Aug 17, 2021
@raulk raulk unassigned vyzo Aug 17, 2021
@raulk raulk added tribute and removed tribute labels Aug 17, 2021
@raulk
Copy link
Member

raulk commented Aug 17, 2021

Closed in #5767.

@raulk raulk closed this as completed Aug 17, 2021
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

Successfully merging a pull request may close this issue.

4 participants