[Feature flag] Rollout of `api_v3_repos_events_optimization`
What
Remove the :api_v3_repos_events_optimization
feature flag.
Owners
- Team: ~"group::ecosystem"
- Most appropriate slack channel to reach out to:
#g_create_ecosystem
- Best individual to reach out to: @.luke
Expectations
What are we expecting to happen?
We should see the number of SQL queries to the /api/v3/repos/:namespace/:project/events
endpoint drop #321839 (closed).
What might happen if this goes wrong?
We might find that the overall SQL latency of the endpoint actually increases.
What can we monitor to detect problems with this?
-
Kibana for the API route (paying attention to
json.db_count
,json.duration_s
andstatus
values) - Grafana Rails Controller dashboard for the endpoint
Beta groups/projects
If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.
-
gitlab-org/gitlab
project
Roll Out Steps
-
Enable on staging ( /chatops run feature set feature_name 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 feature_name 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. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code -
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 api_v3_repos_events_optimization false
Edited by Luke Duncalfe