Skip to content

[FF] log_refresh_service_duration --

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

This issue tracks the rollout of the log_refresh_service_duration feature flag.

Rollout Steps

Rollout on non-production environments

  • Ensure that the feature MRs have been deployed to non-production environments.
  • Enable the feature globally on non-production environments.
  • Test the feature on staging and verify it works as expected.
  • Verify there are no new errors or performance regressions.

Rollout on Production

Preparation

  • Ensure that the feature MRs have been deployed to GitLab.com.
  • Check if the feature flag change needs to be accompanied by a change management issue. Cross link the issue here if it does.
  • Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the @sre-oncall Slack alias.

Rollout

  • Enable the feature globally on production environment.
  • Monitor for any new errors or performance regressions.
  • Announce the feature flag rollout in #f_ Slack channel.

Cleanup

  • Remove the feature flag and associated code.
  • Update documentation if needed.

Rollback Plan

If issues are discovered during rollout:

  1. Disable the feature flag immediately
  2. Investigate the issue
  3. Fix and redeploy if necessary
  4. Resume rollout once the issue is resolved
Edited by 🤖 GitLab Bot 🤖