-
Notifications
You must be signed in to change notification settings - Fork 30
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
Extend /health endpoints to make them async and detailed #54
Comments
karntrehan
changed the title
Extend /health endpoints for monitoring kafka for 500 error when an event happens
Extend /health endpoints to make them async and detailed
Apr 6, 2023
@chinmoy12c to document the schema here. Some tests need to be fixed. |
Pr raised. @pankajjangid05 & @surabhi-mahawar to review. |
The response JSON schema needs to be changed. @tushar5526 please add the required schema. |
The /health schema should follow this template response, so that we can get the status of dependent services as well. Response Format - https://yaus.xyz/health |
@chinmoy12c These PRs are merged. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current /health endpoints of services are not very intuitive. They are also synchronous leading to blockages of 4 seconds on each call to /health.
We should make them async and also check internal working like kafka giving 500s.
The text was updated successfully, but these errors were encountered: