-
Notifications
You must be signed in to change notification settings - Fork 14
Blog post about our status page #496
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good! I want to ask for input from any community members who read it - and I'm not clear whether to generate a CSAT survey or just have people respond via FD.
CSAT's typically go with feature announcement blogs- https://docs.google.com/document/d/1bH5fN2lXcZ-vjQ4Pb4lfaeQbmoCBkN1QYjA7ZaxkmsY/edit?tab=t.dxyyjksnpswv
|
||
As part of this process, we've also [streamlined our incident response processes](https://github.com/2i2c-org/team-compass/pull/1021) in order to more quickly respond to outages when they occur (ideally, before a community has even noticed!). | ||
|
||
There are still plenty of improvements we'd like to make: for example, we're focusing on major outages right now, but would like to extend some level of reporting for _degraded_ service, like unexpectedly slow start times. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd love feedback from communities on this one - should we use the CSAT form? Have them contact us via support@2i2c.org?
There are still plenty of improvements we'd like to make: for example, we're focusing on major outages right now, but would like to extend some level of reporting for _degraded_ service, like unexpectedly slow start times. | |
There are still plenty of improvements we'd like to make: for example, we're focusing on major outages right now, but would like to extend some level of reporting for _degraded_ service, like unexpectedly slow start times. We'd love to hear feedback. If you use our network of hubs and have suggestions for status page improvements, reach out to our [support team](https://docs.2i2c.org/support/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a button for feedback at the top, so I'll not merge this change in!
Co-authored-by: aprilmj <147750733+aprilmj@users.noreply.github.com>
Co-authored-by: aprilmj <147750733+aprilmj@users.noreply.github.com>
Co-authored-by: aprilmj <147750733+aprilmj@users.noreply.github.com>
Co-authored-by: aprilmj <147750733+aprilmj@users.noreply.github.com>
This adds a little blog post about our status page, and fixes redirects while we're at it!
As part of this, I've made
status.2i2c.org
redirect to the pagerduty link and noted it here👉 Link to post