Proposal: When an Incident is declared, output the latest changed feature flags into the incident issue
When an incident is declared we have some automation that takes place via woodhouse. I'd like to request that we expand this to include grabbing X number of feature flags over the course of the past Y hours automatically indicated in the incident. Doing so may assist more quickly identifying if a feature flag change can be the root cause of an incident.
We already provide a link to a search for all events that are logged: https://nonprod-log.gitlab.net/goto/2f2872632ccd39c3895e11290c77c346 as part of the template in the incident issue. However, one must search immediately to narrow down results that are immediately provided
Proposals
-
Ask woodhouse to drop the last X number of feature flags over the course of Y time into the incident issue as a comment -
Breakout our Kibana search into many that include configuration changes from infrastructure, deployments, feature flags -
Improve our ElasticSearch data such that information that is actually a URL, is stored as a URL instead of a string. This supposedly enables clickable links inside of Kibana -
feature flag changes should have links in Kibana to the issue that is logged here: https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/-/issues/ -
...
Edited by John Skarbek