FY25 Q2 - SaaS Platforms Shared PIs
The purpose of this issue is to propose and discuss Performance Indicators (PIs) that are shared across Sub-DepartmentSaaS Platforms . Most notably when working on OKRs, we struggle to come up with measurable objectives for the team - either because we are not sure what is important to measure, or we don't have a mechanism in place to do the measurement. By aligning PIs with OKRs, roadmap and team direction, we can ensure the output of the team is positively impacting the areas we think are important.
There is currently 3 shared PIs listed for the section on the SaaS Platforms Performance Indicators page:
GitLab.com Availability SLO : Percentage of time during which GitLab.com is fully operational and providing service to users within SLO parameters. Definition is available on the GitLab.com Service Level Availability page. Historical Availability is available on the Service Level Availability page.
Mean Time To Production (MTTP) Measures the elapsed time (in hours) from merging a change in gitlab-org/gitlab projects master branch, to deploying that change to gitlab.com. It serves as an indicator of our speed capabilities to deploy application changes into production.
Corrective Action SLO The Corrective Actions (CAs) SLO focuses on the number of open severity::1/severity::2 Corrective Action Issues past their due date.
Suggestions
💰 Cost
- Cost per user of gitlab.com
😍 User Experience
- User Satisfaction Score
🛠 Infrastructure Scalability
- Number of contributors to instrumentor
Others
- Example