[Feature flag] Enable generic alert fingerprinting
What
Remove the :generic_alert_fingerprinting
feature flag ...
Owners
- Team: devopsmonitor ~"group::health"
- Most appropriate slack channel to reach out to:
#g_monitor_health
- Best individual to reach out to: @seanarnold
Expectations
### What are we expecting to happen?
FF removal will cause alerts to be grouped by fingerprint
What might happen if this goes wrong?
- Sentry errors
- User behaviour does not meet expectations
What can we monitor to detect problems with this?
- View Sentry errors
- Ensure we test alerting with expected outcomes
Beta groups/projects
As discussed in !34820 (diffs, comment 368116761) enabling an implicit feature flag (feature flag name == license name) is not not possible.
We need to enable the feature flag globally then.
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com globally -
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 by Sean Arnold