-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: health check #104
feat: health check #104
Conversation
8f36860
to
dec49b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall great PR, very well documented. I'm leaving some comments but most of them are optional.
txstratum/healthcheck/healthcheck.py
Outdated
health_check = ComponentHealthCheck( | ||
component_name=self.COMPONENT_NAME, | ||
component_type=ComponentType.FULLNODE, | ||
# TODO: Ideally we should not use private fields. We'll fix this when fixing line 170 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest naming the feature/command that is currently on line 170, as the line can change on maintenance PRs.
Co-authored-by: Tulio Miranda <tulio.mir@gmail.com>
20d55c5
to
d1b591b
Compare
Acceptance Criteria
We should have a new
/health
endpoint, that will implement a more complex health check which includes:/v1a/version
endpoint is responding. In future PRs we will use the new yet-to-be-implemented/v1a/health
endpoint of hathor-core.