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

[autoendpoint] Respond to /health with database health #169

Closed
AzureMarker opened this issue Jun 29, 2020 · 0 comments · Fixed by #183
Closed

[autoendpoint] Respond to /health with database health #169

AzureMarker opened this issue Jun 29, 2020 · 0 comments · Fixed by #183
Assignees
Labels
2 Estimate - Small

Comments

@AzureMarker
Copy link
Contributor

The /health route should check the health of the router and message tables and include the results in the response. Additionally, the number of clients should be included.

These requirements are based on the behavior of the Python autoendpoint application, specifically health.py.

We may want to use this handler for the /__heartbeat__ endpoint as well. According to the Dockerflow docs, that endpoint should also return application health information: https://github.com/mozilla-services/Dockerflow#containerized-app-requirements

@AzureMarker AzureMarker added this to the Autoendpoint Rust Server milestone Jun 29, 2020
@AzureMarker AzureMarker self-assigned this Jun 29, 2020
@AzureMarker AzureMarker added the 2 Estimate - Small label Jun 29, 2020
@AzureMarker AzureMarker linked a pull request Jul 13, 2020 that will close this issue
AzureMarker added a commit that referenced this issue Jul 27, 2020
Also changed the `/__heartbeat__` handler from `/status` to `/health`.

Closes #169

Co-authored-by: Philip Jenvey <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 Estimate - Small
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant