Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate options for creating a banner for outages/slowness #1503

Closed
Tracked by #113
lbeaufort opened this issue Nov 16, 2017 · 0 comments
Closed
Tracked by #113

Investigate options for creating a banner for outages/slowness #1503

lbeaufort opened this issue Nov 16, 2017 · 0 comments

Comments

@lbeaufort
Copy link
Member

lbeaufort commented Nov 16, 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.

@AmyKort AmyKort added this to the RBS 1 (Reliability, stability and bugs) milestone Nov 20, 2017
@AmyKort AmyKort changed the title Create a banner for outages/slowness Investigate options for creating a banner for outages/slowness Nov 21, 2017
@AmyKort AmyKort removed this from the RBS 1 (Reliability, stability and bugs) milestone Nov 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants