Enhance "FOC Status page"

[BigLep]

Done Criteria

The FOC status page (currently status.filoz.org) has been updated such that:

1. Rename it to emphasize Filecoin Cloud (e.g., “Filecoin Cloud Status”)
   • URL can still be filoz.org if necessary, but it would be ideal to be status.filecoin.cloud to drive the message home.
2. Add a visible status page link on filecoin.cloud filecoin-cloud#283
3. Have a way to surface other significant issues besides websites being down (e.g., contract upgrade schedule, significant number of SPs down, IPNI down)
4. Add Subscribe capability. Users can subscribe to incidents (email or similar).
5. Add Contact us button: - Allows reporting “I see a problem” directly from status page. - Could feed into whatever is devised for Create and implement plan for users to easily file "FOC problems" #17
6. Don't lose state across cluster restarts: https://github.com/FilOzone/infra/issues/65

Why Important

Helps ensure users have a clear canonical place to find the high-level status of FOC.

Notes

[rjan90]

I started looking into this issue ticket in https://github.com/FilOzone/infra/pull/107. But I have some questions with regards to a couple of the acceptence criteria:

Add a link on the Filecoin Cloud site.
(bonus) Ideally the link on filecoin.cloud changes if status.filecoin.cloud is not all green.

Is that meant to be a link from filecoin.cloud to the status page, or a link from the status page back to filecoin.cloud? If so I can separate this out to its own ticket in the Filecoin-Cloud website repo for better tracking.

Add Subscribe capability. Users can subscribe to incidents (email or similar).

I could not see Gatus offering any Subscribe capability, so we need to think deeper about what we want to do here. One open question is if we should move the public status page to Better Stack to use its native subscriber and status-update features instead? But then we loose the effort spent on setting up Gatus (and its built-in capabilities)

[BigLep]

Thanks @rjan90 !

Is that meant to be a link from filecoin.cloud to the status page?

Yeah, that's right. We want to increase visibility of the status page. There should be a link from filecoin.cloud → status.filecoin.cloud. Creating an issue in filecoin-cloud repo sounds good!

I could not see Gatus offering any Subscribe capability, so we need to think deeper about what we want to do here. One open question is if we should move the public status page to Better Stack to use its native subscriber and status-update features instead? But then we loose the effort spent on setting up Gatus (and its built-in capabilities)

Good to know. Independent of dev resources, are there any advantages of Gatus vs. BetterStack status page? Beyond the subscribe capability, is there other things we get to move to BetterStack status pages?

Accounting for dev resources, how big of a lift is it to get to BetterStack?