Remove collect_package_events_redis feature flag
What
Remove the : collect_package_events_redis
feature flag.
Owners
- Team: package
- Most appropriate slack channel to reach out to:
#s_package
- Best individual to reach out to: @ggelatti
Expectations
What are we expecting to happen?
Redis counter events are expected to start happening, triggered by package events (publish a package, etc).
What might happen if this goes wrong?
Redis load too high.
What can we monitor to detect problems with this?
Monitor redis.
Beta groups/projects
N/A
Roll Out Steps
-
Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department) -
Enable on staging ( /chatops run feature set collect_package_events_redis true --staging
) -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --project=gitlab-org/gitlab feature_name true
) -
Coordinate a time to enable the flag with the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set collect_package_events_redis true
) -
Cross post chatops Slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
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 --project=gitlab-org/gitlab collect_package_events_redis false
Edited by David Fernandez