[Feature flag] Rollout of `product_analytics_tracking`
What
Remove the :product_analytics_tracking
feature flag introduced by !46482 (merged).
Owners
- Team: Product Analytics
- Most appropriate slack channel to reach out to:
#g_product_analytics
- Best individual to reach out to:
@ali-gitlab
Expectations
What are we expecting to happen?
Enabling this feature will cause a copy of some backend Snowplow events to be sent to the Product Analytics collector. Currently, the ProductAnalytics
tracking destination only allows one event (promotion of issue to epic) to be sent. In the future, there could be more events allowed.
In order for this feature to work correctly, the product_analytics
FF must be enabled for the self-monitoring project.
What might happen if this goes wrong?
If a high volume of events are being sent, this could cause lots of traffic to the Product Analytics collector, as well as the database.
What can we monitor to detect problems with this?
Beta groups/projects
This feature affects the entire instance, since we do not currently have granular control over which groups send Snowplow events.
Roll Out Steps
-
Enable on staging ( /chatops run feature set product_analytics_tracking true --staging
) -
Test on staging -
Enable on GitLab.com ( /chatops run feature set product_analytics_tracking true
) -
Announce on the issue that the flag has been enabled -
Wait for product_analytics
FF to be removed -
Ensure that documentation has been updated -
Remove feature flag and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set product_analytics_tracking false