jimleroyer commented 2 years ago

Description

As a user of Notify, I need to know its status and maintenance windows, So that I know if the software works correctly and when Notify has planned maintenance.

WHY are we building?

To improve Notify status communication with our users.

WHAT are we building?

A status/maintenance page.

VALUE created by our solution

Better communication and more transparency. Being able to update information in a fast-moving incident more easily. Reduce # of emails sent to client inboxes. More efficient workflow in an incident.

Stakeholders who want to know about an incident but aren't a client will be able to get information

Supports self-serve

Acceptance Criteria** (Definition of done)

[x] Feature request: it would be useful to have hour and not just date for issues on the system status page (and a timestamp on the resolution update)
[x] Status page is up and running.
[x] It is easily reachable and advertised through the main website.
[x] Maintenance windows can be communicated on the status page (future release, covered by #1414)
[x] Notify components (API / admin) status is communicated on the page.
[x] Templates for common issues and incidents are created and translated ready to use (separate release, covered by #1205)
[x] "This page is a work-in-progress" caveat is removed in EN and FR

QA Steps

[x] Check reported status fits with actual status of the components.
[x] Emulate a maintenance window and check on the new status page.
[x] Emulate a bad component status report on the status page (triggering some errors on purpose).

Additional Info

Max and team tried out the upptime library and deployed it over there. Follow this link to see the Slack conversation that provides a bit more info and context.
We could add a banner to the main page when the status page shows something ongoing.
Related Research
Hit an issue and did not know what was causing the problem / how they can fix it