-
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
what other okcomputer checks do we need? #339
Comments
Not feeling fedora/WFS checks. As infrequently as this app is actively used, those alerts aren't going to as be meaningful as just getting the honeybadger exceptions. |
fair point. easy enough to reopen this and add more checks if needed. closing this one. |
ok, actually, @atz says maybe add a redis check, because it's cheap (box on the same machine, canned check available or at least pattern from pres cat, so cheap both in terms of resource usage and dev time). reopening and putting in backlog. |
@atz also points out that we can make some checks optional, if we want the status info, but don't want to give pager alerts for them (e.g. connection to fedora at 5 am when no one's using the app) |
stub initial implementation indicates:
# by default, okcomputer does "app up?" and "database conntected?" checks
see #334
other possibilities:
The text was updated successfully, but these errors were encountered: