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

Health check #81

Open
aspic opened this issue Mar 13, 2021 · 3 comments
Open

Health check #81

aspic opened this issue Mar 13, 2021 · 3 comments
Labels
question Further information is requested

Comments

@aspic
Copy link
Collaborator

aspic commented Mar 13, 2021

Could it be an idea to have a health-check endpoint? This endpoint could carry out a number of checks to ensure that the Node is behaving properly as for instance:

  • RPC call to see that the node is responding
  • RPC call to check node values (not sure what is most relevant endpoint/metrics here)
  • Let proxy perform a send and listen for receive to make sure that blocks are broadcasted accordingly (advanced)

What are your thoughts?

@aspic aspic added the question Further information is requested label Mar 13, 2021
@Joohansson
Copy link
Owner

Maybe. I'm currently using uptimerobot.com and calling https://proxy.nanos.cc/proxy/?action=version and reacting to the expected response. I know if the node or proxy goes down because I also have a similar test for the nodeMonitor software. So personally I'm not in need of such tool.

How would the heath-check notify you?

@aspic
Copy link
Collaborator Author

aspic commented Mar 15, 2021

Uptimerobot would still serve the "notification", but it could check a /health endpoint which could have some more sophisticated tests (configurable of course), in addition to the version-action or other relevant RPC checks.

@Joohansson
Copy link
Owner

Ok, then it makes more sense! I'm positive

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

No branches or pull requests

2 participants