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

what other okcomputer checks do we need? #339

Closed
jmartin-sul opened this issue Sep 21, 2018 · 4 comments
Closed

what other okcomputer checks do we need? #339

jmartin-sul opened this issue Sep 21, 2018 · 4 comments

Comments

@jmartin-sul
Copy link
Member

stub initial implementation indicates:

# by default, okcomputer does "app up?" and "database conntected?" checks

see #334

other possibilities:

  • can connect to fedora?
  • can connect to WFS?
  • can read from... ?
  • can write to... ?
    • adequate space in... ?
@atz
Copy link
Contributor

atz commented Sep 22, 2018

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.

@jmartin-sul
Copy link
Member Author

fair point. easy enough to reopen this and add more checks if needed. closing this one.

@jmartin-sul
Copy link
Member Author

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.

@jmartin-sul jmartin-sul reopened this Sep 24, 2018
@jmartin-sul
Copy link
Member Author

@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants