Skip to content
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.

more involved liveness checks #400

Open
codl opened this issue Feb 23, 2021 · 0 comments · May be fixed by #418
Open

more involved liveness checks #400

codl opened this issue Feb 23, 2021 · 0 comments · May be fixed by #418

Comments

@codl
Copy link
Owner

codl commented Feb 23, 2021

on top of #120, it would be useful if the health check also performed some smoke tests like

  • has there been a successful delete in the last minute? → is there at least one account with last_delete sometime within the last minute?
  • same with fetch, refresh
  • is there an abnormal amount of accounts with high backoff levels? this one would need additional monitoring to measure what is "normal" as mastodon instance churn likely means it keeps going up. I'm not sure it's worth it
  • others?

probably would be wise to only trip these tests if there are more than a few accounts, so that a new install doesn't keep raising flags just because there aren't enough accounts to keep it busy

@codl codl linked a pull request Mar 13, 2021 that will close this issue
@codl codl linked a pull request Mar 4, 2022 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant