[Feature flag] Enable Escalating manually created incidents
Summary
This issue is to rollout Escalating manually created incidents on production,
that is currently behind the incident_escalations
feature flag.
Owners
- Team: Monitor devopsmonitor
- Most appropriate slack channel to reach out to:
#s_monitor
- Best individual to reach out to: @seanarnold / @crystalpoole
- PM: @abellucci
Stakeholders
Expectations
What are we expecting to happen?
Manually created incidents will escalate based on the Escalation Policy for the project.
What might happen if this goes wrong?
Escalations will not reach their intended recipients.
What can we monitor to detect problems with this?
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 <feature-flag-name> 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.
Specific rollout on production
- Ensure that the feature MRs have been deployed to both production and canary.
- Enable for project-actor:
-
/chatops run feature set --project=gitlab-examples/ops/incident-setup/everyone/tanuki-inc incident_escalations true
-
-
Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.
Preparation before global rollout
-
Check if the feature flag change needs to be accompanied with a change management issue. Cross link the issue here if it does. - N/A -
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). - !80441 (merged) -
Announce on the feature issue an estimated time this will be enabled on GitLab.com. -
If the feature might impact the user experience, notify #support_gitlab-com
and your team channel (more guidance when this is necessary in the dev docs). - N/A
Global rollout on production
For visibility, all /chatops
commands that target production should be:
-
Executed in the
#production
slack channel. -
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 has an actor, perform actor-based rollout.
-
/chatops run feature set incident_escalations 50 --actors
-
- Enable the feature globally on production environment.
-
/chatops run feature set incident_escalations true
-
- If the feature flag in code has an actor, perform actor-based rollout.
-
Announce on the feature issue that the feature has been globally enabled.
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.
-
Create a merge request to remove incident_escalations
feature flag. Ask for review and merge it. - !80444 (merged)-
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. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
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 incident_escalations --dev
-
/chatops run feature delete incident_escalations --staging
-
/chatops run feature delete incident_escalations
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set incident_escalatations false