-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Healthcheck Endpoint #91
Comments
There's no scenario where MIND could go wrong and it being acceptable, so any errors should simply be fixed. Do you have logs of the error? |
Unfortunately, this was a little time back so no. But there was an error. The homepage was working but actually logging in had stopped. I restarted the container and it was working again and all the reminders that had been missed came through instantly. I was not alerted that Mind was down because my monitoring system curls the homepage URL, so as far as it was concerned it was all working. |
Hmm sounds like the thread that handles the sending of reminders on time crashed when handling one of the reminders. I could refactor it so that it always stays alive, even when an error occurs. The error should of course be fixed, but at least operation is continued. |
Right, in the meanwhile I have established that monitoring the /api/settings path suffices since it does not need password auth. |
So maybe nothing further is needed on this suggestion? Since /api/settings acts like a health path anyway |
Is your feature request related to a problem? Please describe.
No, just a feature that would be handy.
Describe the solution you'd like
Could we add a health check endpoint in the API that could be probed at all? Currently I use the default home page to probe it but I have found this can be unreliable as Mind has crashed before behind the scenes yet the homepage was still up.
Additional context
The text was updated successfully, but these errors were encountered: