Update events migrated from RedisHLL to Snowplow with new context
Problem
While migrating events from Redis to Snowplow we discovered together with the data team that they need additional context in order to unify the migrated metrics in downstream systems. Since this was discovered in an ongoing effort many of the already migrated events do not have the new context yet.
Desired outcome
All already migrated events have the context so they are usable for the Data team
Overview
- usage_activity_by_stage_monthly.create.action_monthly_active_users_project_repo (RedisHLL)
-
has not been migrated yet -
has been checked for context -
has context already implemented - Issue for context #371801 (closed). It looks that this event is already tracked see https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/event_create_service.rb#L223
-
- redis_hll_counters.user_packages.user_packages_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - Issue for context #371801 (closed)
-
- redis_hll_counters.analytics.g_analytics_valuestream_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.ci_templates.ci_templates_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - Issue for context: #371803 (closed)
-
- redis_hll_counters.issues_edit.issues_edit_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.terraform.p_terraform_state_api_unique_users_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.incident_management.incident_management_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.search.i_search_paid_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - Issue for context: #371803 (closed)
-
- usage_activity_by_stage_monthly.create.merge_requests_users (RedisHLL)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- usage_activity_by_stage_monthly.create.action_monthly_active_users_ide_edit (RedisHLL)
-
has not been migrated yet -
has been checked for context -
has context already implemented - add context at https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/editor_unique_counter.rb#L51
-
- redis_hll_counters.search.search_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - Issue for context: #371803 (closed)
-
- usage_activity_by_stage_monthly.create.action_monthly_active_users_design_management (RedisHLL)
-
has not been migrated yet -
has been checked for context -
has context already implemented - add context at https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/event_create_service.rb#L264
-
- redis_hll_counters.ecosystem.ecosystem_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - it seems to uses umbrella label instead of component events to create aggregation. It would be required to split this umbrella tracking into each of component event ones
-
- redis_hll_counters.compliance.compliance_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.epics_usage.epics_usage_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - it seems to uses umbrella label instead of component events to create aggregation. It would be required to split this umbrella tracking into each of component event ones
-
- redis_hll_counters.compliance.g_compliance_dashboard_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- redis_hll_counters.code_review.i_code_review_user_approve_mr_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - add at https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/merge_request_activity_unique_counter.rb#L81
-
- redis_hll_counters.issues_edit.g_project_management_issue_iteration_changed_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - adding at !103534 (merged)
-
- redis_hll_counters.issues_edit.g_project_management_issue_milestone_changed_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented - adding at !103534 (merged)
-
- redis_hll_counters.analytics.analytics_total_unique_counts_monthly (RedisHLL events based)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- counts.commit_comment (Redis)
-
has not been migrated yet -
has been checked for context -
has context already implemented
-
- counts.source_code_pushes (Redis)
-
has not been migrated yet -
has been checked for context -
has context already implemented - add at https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/workers/post_receive.rb#L145
-
Edited by Sebastian Rehm