Right now we have an outage on Sentry and all I get is hanging requests, hence a hanging CLI. I propose we do the following:
- Add a sensible timeout for our API requests, especially the ones we know should respond quickly
- Add the
sentry status command group that uses https://status.sentry.io/ as its backend
- Either automatically check sentry API status and report that while also supressing the reporting of any 5xx API errors upstream or at least provide
sentry status command as a tip
All items after item 1 only seem to apply to SaaS. However, if self-hosted has a proper health endpoint which I think it does, we can add some cursory support to that. In fact, if that health endpoint exists for SaaS publicly, that can be the common thing and status.sentry.io can be the extended version for SaaS.
Right now we have an outage on Sentry and all I get is hanging requests, hence a hanging CLI. I propose we do the following:
sentry statuscommand group that uses https://status.sentry.io/ as its backendsentry statuscommand as a tipAll items after item 1 only seem to apply to SaaS. However, if self-hosted has a proper
healthendpoint which I think it does, we can add some cursory support to that. In fact, if that health endpoint exists for SaaS publicly, that can be the common thing and status.sentry.io can be the extended version for SaaS.