[Feature flag] Enable `ci_lower_frequency_trace_update`
What
Rollout and then remove :ci_lower_frequency_trace_update
feature flag.
Owners
- Team: ~"group::continuous integration"
- Most appropriate slack channel to reach out to:
#rapid-action-verify-db-queries
and#g_ci
- Best individual to reach out to: @fabiopitino
Expectations
What are we expecting to happen?
This will reduce by half the rate of requests for both PUT /jobs/:id
and PATCH /jobs/:id/trace
endpoints that the Runner uses to communicate back to GitLab. The default interval between requests was previously 30 seconds, the feature flag increases it to 60 seconds.
What might happen if this goes wrong?
We don't expect anything bad to happen since the value is used as is by the Runner to send back the next update of the status or trace.
What can we monitor to detect problems with this?
Data to monitor: rate of requests of PUT /jobs/:id
and PATCH /jobs/:id/trace
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 -
gitlab-org
/gitlab-com
groups - ...
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 --project=gitlab-org/gitlab feature_name false