Proposal: Add runway service to service catalog
Context
As more services are onboarded during Runway beta, ~"team::Frameworks" must provide a stable user experience by monitoring and operating Runway at a platform-level. Right now, Runway relies on the following GCP services:
Eventually, Runway will also rely on the following GCP services:
- Google Memorystore for Redis (https://gitlab.com/gitlab-com/gl-infra/platform/runway/team/-/issues/62)
- Google Cloud SQL (#54)
Additionally, Runway depends on the following GitLab.com services:
Each of these services emit metrics that can be used for SLIs. In the future, we can also build on SLIs w/ custom metrics, e.g. failed deployments, rollbacks, etc.
Proposal
Add new runway
service to service catalog owned by ~"team::Frameworks" to build SLIs/SLOs, dashboards, and documentation that are required for operating Runway the platform.
Worth noting: Not to be confused w/ services that are managed by Runway. Runway service owners are only concerned w/ application-level metrics, not infrastructure outside of their control.