-
Notifications
You must be signed in to change notification settings - Fork 12
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
feature: Add health check endpoint #24
Labels
enhancement
New feature or request
Comments
Would definitely take a PR, not sure when I have time to implement that, pretty busy right now... Ideally it'd also expose some Prometheus metrics with failures and such I think so you can set up alerting |
cromefire
changed the title
IMPROVEMENT: Add health check endpoint
feature: Add health check endpoint
Jan 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, great project! This enhancement request should be pretty easy to implement.
For added resiliency, add a health check endpoint to validate that the updater is actually running.
Proposed endpoints could be /health or /alive, with a simple HTTP 200 as the response code. Maybe add an "ok" in the body.
Bonus points: A JSON response which lists if the last communication attempts to the Fritz!Box and Cloudflare were successful. Still keep the 200 response code, even if these connections were not successful.
The text was updated successfully, but these errors were encountered: