Performance Indicator for Pipeline Execution
Background
The current performance indicator is number of unique users who trigger ci_pipelines
.
As FY23 starts and after the recent review of possible projects we should also ensure we're tracking right performance indictor for the group for the year.
The FY23 product themes includes "Extend our lead in CI/CD". The PI to track this for the year is CMAU (Sum of Ops Section SMAU(Stage Monthly Active Users)) with a goal of doubling that value from 1.8M to 3.6M. Areas in which the section will focus to do this that are of interest to Pipeline Execution are:
- Ensuring we provide a scalable and efficient CI service
- Providing a robust Cloud Runner service to enable GitLab CI on GitLab hosted platforms
Is unique users who trigger ci_pipelines still the right thing to measure?
The purpose of this issue is to start discussion with the group about if this is still the right thing for us to measure. The Performance Indicator for the group should be a leading indicator. A note from the internal handbook "For GMAU and SMAU there is a desire for these metrics to be the unique users across the aggregate of associated AMAU's but current limitations in how we receive usage ping data (already aggregated per event) means that is not currently possible."
Next Steps
- Ideate on new metrics to track - tied back to epics/issues targeted for the year - PE team
- Add comments below for possible new metrics.
- Decide on changing to a new metric/keeping the existing
- Update dashboard for additional feature tracking and update the performance indicator as needed.