Skip to content

[Beta Feature flag] Enable Status Page MVC by default

What

Remove the implicit feature flag (beta_feature_available?(:status_page)) for Status Page MVC.

Note that :status_page is also used as a license check for GitLab Ultimate hence it's "implicit" (see https://docs.gitlab.com/ee/development/feature_flags/development.html for more context).

For for more context see !26710 (comment 302546523) where the feature flag was added.

See &2479 (closed) for the Status Page MVC 1 epic.

Owners

  • Team: Monitor:Health
  • Most appropriate slack channel to reach out to: #g_monitor_health
  • Best individual to reach out to: @splattael @seanarnold

Expectations

Make Status Page available to users so they can publish incidents to a S3 bucket. See &2479 (closed) for more context.

### What are we expecting to happen?

  • Make Settings > Operations > Status Page available so users can configure and enable the Status Page functionality per project
  • Each issue, note, or note emoji change will trigger a background job to publish the content to a CDN

What might happen if this goes wrong?

  • We may trigger to many background jobs which might overload sidekiq queue
  • The used SQL queries might be too slow
  • Potential sensitive information (in issue title, description or note) can be publish on the CDN
  • Publishing to CDN may fail

What can we monitor to detect problems with this?

We could monitor sidekiq jobs, database load on gitlab.com

Beta groups/projects

This feature will be tested on gitlab.com.

Roll Out Steps

  • Enable on staging
  • Test on staging
  • Ensure that documentation (!26751 (merged)) has been updated
  • [-] Enable on GitLab.com for individual groups/projects listed above and verify behaviour
    • There's not way to enable a beta feature flag per group/project
  • Coordinate a time to enable the flag with #production and #g_delivery on slack.
  • Announce on the issue an estimated time this will be enabled on GitLab.com
  • Enable on GitLab.com by running chatops command in #production
  • Cross post chatops slack command to #support_gitlab-com and in your team channel
  • Announce on the issue that the flag has been enabled
  • Remove feature flag and add changelog entry (!28966 (merged))
  • After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel
Edited by Peter Leitzen