## Overview - While [Internal Events](https://docs.gitlab.com/ee/development/internal_analytics/internal_event_instrumentation/) don't fully meet all our requirements per task (1), it gives us two other benefits: - For `GitLab.com`, we can send the data to Snowplow and query it into Tableau. Snowplow keeps the data history for all time and also allows us to specify properties such as `component_id` and `component_name`. This means that for `GitLab.com` we're recording usage data both in the local PostgreSQL table as well as Snowplow. - This allows us to visualize the data sooner than waiting for the possible internal dashboard feature to be designed/implemented (ref: https://gitlab.com/gitlab-org/gitlab/-/issues/440382#note_1793005911). - For self-managed instances, we can still make use of Internal Events' RedisHLL counters to give us a unique count of projects that used _any_ component. So we can't get as much granularity but it may still be useful to monitor. ## Implementation ### Step 1 Add Internal Event for monitoring when a component is included in a pipeline. Include `component_name` and all aggregations possible to record. ### Step 2 Query and visualize the data in Tableau. Moved to its own issue: https://gitlab.com/gitlab-org/gitlab/-/issues/454912. ## MR Implementation | Step | Link | Details | | ------ | ------ | ------ | | [1](https://gitlab.com/gitlab-org/gitlab/-/work_items/443382#step-1) | https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147378+ | Preparation for tracking the included catalog components in a pipeline. | | | https://gitlab.com/gitlab-org/gitlab/-/merge_requests/146834+ | Internal event tracking applied. Event name: `ci_catalog_component_included`. Behind FF: `Enable ci_track_catalog_component_usage`. Roll-out issue: https://gitlab.com/gitlab-org/gitlab/-/issues/446290 | ## UPDATE [2024-04-08] Creating visualizations of the data in Tableau has been moved to its own issue: https://gitlab.com/gitlab-org/gitlab/-/issues/454912.