Recreate Redis Counters using Snowplow events - Phase 2: Wave 2
Summary
In &7493 (closed), we instrumented the first set of Redis Counters using Snowplow events in SaaS. This is the 2nd wave of counters to be instrumented using Snowplow Events.
-
analytics_unique_visits.analytics_unique_visits_for_any_target_monthlyEDIT: this is a self-managed only feature and is not available in SaaS, therefore we will remove this metric from the project
-
redis_hll_counters.terraform.p_terraform_state_api_unique_users_monthly -
counts.static_site_editor_views -
redis_hll_counters.search.i_search_paid_monthly
-
analytics_unique_visits.analytics_unique_visits_for_any_target_monthlyEDIT: Duplicate of metric 1 above
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/13208
Data Availability
The aggregate metrics can be found in SiSense in the following tables per this comment.
-
mart_product_usage_paid_user_metrics_monthly_workspace
table - Gainsight/Customer Success -
redis_namespace_snowplow_clicks_aggregated_workspace
table - the redis events themselves that Product Data Insights can query and also what feeds the above referenced Gainsight data model.
Edited by Amanda Rueda