Create new Service Ping metrics to track CI Leading Indicators
What does this MR do and why?
We want better insights into pipelines that are being created, see #429942
- Adds the
source
(e.g. a push) and theconfig_source
(e.g. a gitlab-ci file) to the properties being tracked for thecreate_ci_internal_pipeline_event
. - Adds metrics to track:
- unique projects that create a pipeline
- unique projects that create a pipeline from a gitlab-ci file
- total number of pipelines being created from a gitlab-ci file
- total number of pipelines being created by schedules
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
How to set up and validate locally
- Run internal events monitor via
rails runner scripts/internal_events/monitor.rb create_ci_internal_pipeline
- You should see an event with
label=web
andproperty=repository_source
- Manually create a CI pipeline in a project through the UI: All the metrics apart from the one counting scheduled pipelines should increase.
- Create a CI pipeline schedule and trigger the schedule. The schedule related metrics should increase. The unique counts for project should not increase if you used the same project as in the last step.
- Trigger a pipeline from a different project to see the
count_distinct_project_id...
metrics increase
Related to #429942
Edited by Sebastian Rehm