Tracking internal ci pipeline creation
What does this MR do and why?
Tracking internal ci pipeline creation
Switching to event based metrics to track pipeline creation
Changelog: performance
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
Updated at 2024-01-26 17:50:19 UTC
Monitored events: create_ci_internal_pipeline
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| RELEVANT METRICS |
+------------------------------------------------------------------------------------+-----------------------------+-----------------------+---------------+---------------+
| Key Path | Monitored Events | Instrumentation Class | Initial Value | Current Value |
+------------------------------------------------------------------------------------+-----------------------------+-----------------------+---------------+---------------+
| counts.count_total_create_ci_internal_pipeline | create_ci_internal_pipeline | TotalCountMetric | 24 | 24 |
| counts.count_total_create_ci_internal_pipeline_monthly | create_ci_internal_pipeline | TotalCountMetric | 24 | 24 |
| redis_hll_counters.count_distinct_user_id_from_create_ci_internal_pipeline_monthly | create_ci_internal_pipeline | RedisHLLMetric | 2 | 2 |
+------------------------------------------------------------------------------------+-----------------------------+-----------------------+---------------+---------------+
+--------------------------------------------------------------------------------------------------------------------------------+
| SNOWPLOW EVENTS |
+-----------------------------+--------------------------+-----------------------+---------+--------------+------------+---------+
| Event Name | Collector Timestamp | Category | user_id | namespace_id | project_id | plan |
+-----------------------------+--------------------------+-----------------------+---------+--------------+------------+---------+
| create_ci_internal_pipeline | 2024-01-26T17:49:17.266Z | InternalEventTracking | 1 | 577 | 290 | default |
| create_ci_internal_pipeline | 2024-01-26T17:49:02.581Z | InternalEventTracking | | 577 | 290 | default |
| create_ci_internal_pipeline | 2024-01-24T17:19:06.753Z | InternalEventTracking | 1 | 1 | 288 | default |
| create_ci_internal_pipeline | 2024-01-24T15:02:43.148Z | InternalEventTracking | 1 | 1 | 288 | default |
| create_ci_internal_pipeline | 2024-01-24T11:03:58.805Z | InternalEventTracking | 1 | 1 | 288 | default |
| create_ci_internal_pipeline | 2024-01-24T09:19:06.643Z | InternalEventTracking | 1 | 1 | 288 | default |
| create_ci_internal_pipeline | 2024-01-24T07:19:03.617Z | InternalEventTracking | 1 | 1 | 288 | default |
| create_ci_internal_pipeline | 2024-01-24T03:19:04.731Z | InternalEventTracking | 1 | 1 | 288 | default |
How to set up and validate locally
Setting up via https://docs.gitlab.com/ee/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.html#internal-events-monitor and then triggering pipelines should update the table in the screenshot
Related to #429065 (closed)
Edited by Max Fan