You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a research issue to determine the best way to inform the public of site outages or periods of slowness. We would want to handle an API outage and a whole-site outage (see this cloud.gov outage)
One option is to create a "status page" in Wagtail where we can update the site status. However, this wouldn't work in case of a cloud.gov outage.
@ccostino had the idea of putting a page in s3 in case of a cloud.gov outage.
The text was updated successfully, but these errors were encountered:
AmyKort
added this to the
RBS 1 (Reliability, stability and bugs) milestone
Nov 20, 2017
AmyKort
changed the title
Create a banner for outages/slowness
Investigate options for creating a banner for outages/slowness
Nov 21, 2017
AmyKort
removed this from the
RBS 1 (Reliability, stability and bugs) milestone
Nov 21, 2017
@LindsayYoung suggested we might want to create a banner for when we're experiencing production issues. Here's an article I found with examples: https://www.smashingmagazine.com/2009/06/effective-maintenance-pages-examples-and-best-practices/
cloud.gov uses statuspage.io: https://cloudgov.statuspage.io/
This is a research issue to determine the best way to inform the public of site outages or periods of slowness. We would want to handle an API outage and a whole-site outage (see this cloud.gov outage)
One option is to create a "status page" in Wagtail where we can update the site status. However, this wouldn't work in case of a cloud.gov outage.
@ccostino had the idea of putting a page in s3 in case of a cloud.gov outage.
The text was updated successfully, but these errors were encountered: