Geo -More detailed site status
Problem to solve
The site status currently indicates healthy or unhealthy. When troubleshooting an unhealthy site, there is very little for a customer to go on to investigate. When the site is unhealthy we should attempt to provide useful insight to what is triggering the state to be unhealthy.
Proposal
When a site is unhealthy, indicate what is believed to be the cause of the the problem. The different errors state could potentially point helpful documentation links that will allow customer to resolve the issue.
The gitlab:geo:check
seems to cover some of the failure conditions. It would be useful to surface this information on the UI on demand to help the customer understand why the site might be unhealthy.
Intended users
Feature Usage Metrics
- The goal is to see a drop in support cases related to site status. Therefore, we will not collect any usage metric directly.
- In future we might want to consider collecting the error state and sending it back via usage ping to understand which error state customers encounter most.
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.