Open PaulKuykendall opened 9 months ago
Blocked tag added: pending the outage summary from https://github.com/cisagov/get.gov/issues/237 (currently pending approval).
This issue has been story pointed and meets DoR criteria. Moving to "Ready"
This one looks like it was initially supposed to be content about an earlier incident, but is perhaps more generalized now? A status or incident reporting page would be useful, but given how long this has been here, wondering if we should revisit or de-prioritize for the time-being? There are some really lightweight options that wouldn't require committing code, but could also provide some level of monitoring that might be worth investigating, too.
@h-m-f-t if you have thoughts!
I would like to do this still. It's not a ton of content work but we should prepare it and then sync it with CISA comms before release.
What is the timeline for this ticket? Is it considered a prioritized ticket?
Issue description
For public trust and transparency, we need to publish some details about service outages when we have information ready to share. As a result, we need to create a space. like a Blog section, to make this system status available.
Acceptance criteria
Additional context
From Cameron: One thing I'd like by the end of next sprint (Sprint 39) is for us to draft some brief content summarizing our availability incident on 1/31. What happened, what we did, what we learned. There is probably some good prior art, maybe https://cloudgov.statuspage.io/history. I haven't made an issue for this, unsure if it's just an A/C on e.g., 1726, but ok if its an issue on it's own. The goal would be to post this on get.gov somewhere. Maybe it's a really brief blog post with a link to a incident history page?
Links to other issues
Examples: Login.gov Cloudflare Cloudflare 2
Blocked by: cisagov/get.gov#237