Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #225205
Closed
Open
Issue created Jun 29, 2020 by Alex Kalderimis@alexkalderimis🔴Maintainer8 of 8 checklist items completed8/8 checklist items

[Feature flag] Enable design activity events

What

Remove the :design_activity_events feature flag ...

Owners

  • Team: ~"group::knowledge"
  • Most appropriate slack channel to reach out to: #g_create_knowledge
  • Best individual to reach out to: @alexkalderimis

Expectations

### What are we expecting to happen?

Nothing - performance may improve due to better SQL queries without the flag

What might happen if this goes wrong?

Performance may be degraded, we might see a rise in 500 errors if DB records cannot be rendered.

What can we monitor to detect problems with this?

  • https://dashboards.gitlab.net/d/rPsQXrImk/rails-controller?orgId=1&refresh=1m
  • https://dashboards.gitlab.net/d/rPsQXrImk/rails-controller?orgId=1&refresh=1m&var-env=gprd&var-type=web&var-stage=main&var-controller=DashboardController&var-action=All

Roll Out Steps

  • Enable on staging
  • Test on staging
  • Ensure that documentation has been updated
  • [-] Enable on GitLab.com for individual groups/projects listed above and verify behaviour
  • [-] 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 (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
Edited Aug 06, 2020 by Alex Kalderimis
Assignee
Assign to
Time tracking