Status Page MVC
Problem to solve
Stakeholder communication is critical for any tech company. Customers needs a portal for their stakeholders to understand status of the services they provide. Operations teams need a portal to communicate those statuses.
A mature status page would contains a list of services provided, description, and status as well as the ability for stakeholders to subscribe to notifications on services as there are changes.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
This work supports the Error Tracking Vision.
Proposal
Building a great service health dashboard will take quite a few releases, but we can show some significant value in a small first iteration.
- When an incident has been created (manually or automatically), provide a button to publish to the status page
- Provide a window of time for a user to either close the incident or manually publish, perhaps 15 minutes. If no action taken, auto-publish an update.
- Once the incident has been marked as resolved, archive the incident to the historical section. For example:
1:00 - 4:20 | <Issue name>
Next steps:
- Templates for status pages so customers can customize the UI
- Proactive communications to subscribers of the dashboard
- Turnkey deployment of runners to check the health of the service from across the world, with packaged alerts
- Key metric displayed, such as availability
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.