[Feature flag] Enable error tracking metrics
Summary
This issue is to rollout #345053 (closed) on production,
that is currently behind the :track_error_tracking_activity
feature flag.
Related MR:
Owners
- Team: grouprespond
- Most appropriate slack channel to reach out to:
#g_respond
- Best individual to reach out to: @syasonik
- PM: @abellucci
Expectations
What are we expecting to happen?
Usage ping includes metrics for unique users to view the error list or error details pages.
When is the feature viable?
!82543 (merged) is merged, feature flag is enabled, and it doesn't destroy redis.
What might happen if this goes wrong?
The flag can be disabled. If something does actually go wrong, that'll be enough & we can come up with a game plan at that time.
What can we monitor to detect problems with this?
The product intelligence grafana dashboard can be monitored for any outrageous sort of scale of events.
Here's a baseline from today: Screen_Shot_2022-03-09_at_5.27.49_PM
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. -
/chatops run feature set track_error_tracking_activity true --dev
-
/chatops run feature set <feature-flag-name> true --staging
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Preparation before global rollout
- Ensure that the feature MRs have been deployed to both production and canary.
-
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. -
Ensure that documentation has been updated (More info). -
Announce on the feature issue an estimated time this will be enabled on GitLab.com.
Global rollout on production
For visibility, all /chatops
commands that target production should be executed in the #production
slack channel and cross-posted (with the command results) to the responsible team's slack channel (#g_respond
).
-
Incrementally roll out the feature. - If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
/chatops run feature set <feature-flag-name> <rollout-percentage>
-
- Enable the feature globally on production environment.
-
/chatops run feature set <feature-flag-name> true
-
- If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
Announce on the feature issue that the feature has been globally enabled. -
Wait for at least one day for the verification term.
Release the feature
After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.
You can either create a follow-up issue for Feature Flag Cleanup or use the checklist below in this same issue.
-
Create a merge request to remove track_error_tracking_activity
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. -
Close the feature issue to indicate the feature will be released in the current milestone. -
Clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete <feature-flag-name> --dev
-
/chatops run feature delete <feature-flag-name> --staging
-
/chatops run feature delete <feature-flag-name>
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set track_error_tracking_activity false