Recreate Redis Counters using Snowplow events - Phase 2: Wave 5
Summary
In &7493 (closed), we instrumented the first set of Redis Counters using Snowplow events in SaaS. This is the 5th wave of counters to be instrumented using Snowplow Events.
-
redis_hll_counters.ecosystem.ecosystem_total_unique_counts_monthlyCovered in https://gitlab.com/gitlab-org/gitlab/-/issues/369090 -
redis_hll_counters.epics_usage.epics_usage_total_unique_counts_monthlyCovered in #366827 (closed) -
redis_hll_counters.code_review.i_code_review_user_approve_mr_monthly -
redis_hll_counters.analytics.analytics_total_unique_counts_monthlyCovered in https://gitlab.com/gitlab-org/gitlab/-/issues/369846 and #373146 (closed) -
counts.source_code_pushes
Note
Please be aware that the Optimize team is creating two additional counters which will be added to the existing GMAU counter: https://metrics.gitlab.com/?q=analytics_unique_visits.analytics_unique_visits_for_any_target_monthly. Please make sure we instrument these new counters as well.
Feature Flag
These events should be instrumented behind a feature flag (separate from the FF used for the first wave of metrics) in case we need to quickly turn off collection.
Next Step
Post delivery, the data team will need to aggregate the snowplow events into counters for use in Sisense and Gainsight. Data team issue for this wave: https://gitlab.com/gitlab-data/analytics/-/issues/13211