Open bfpepper87sentry opened 3 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-settings for triage ⏲️
thanks for the feedback! just to clarify one point you made - you mentioned that "Sentry's feature flag system is overall better". is this referring to how we represent the feature flags as tags right now? if i'm understanding correctly, you like how we present the information but because it is sent as a tag, it's too cluttered, so having a separate tab, with a similar presentation of the info, would help.
@bfpepper87sentry
What we'd want: Ideally a separate tab for "Flags" or something similar to bble to view all of them. The side menu should put feature flags at the bottom so that they do not hide the other more important tags.
Can you elaborate on the problem you're trying to solve by showing Feature Flags all in one place (say, a separate tab). What is the utility of this?
responded to the above question internally.
Problem Statement
We have ~300 feature flags in some sessions and are currently sending them as tags which is Sentry's recommendation. However, this makes the interface VERY noisy and you have to scroll a lot to find the info you need.
Solution Brainstorm
How Bugsnag handles this: Bugsnag has a separate tab for Feature Flags so they don't pollute the UI. Sentry's Feature flag system is overall better, but their visualization as part of "tags" makes them create a lot of clutter and hide other important information. What we'd want: Ideally a separate tab for "Flags" or something similar to bble to view all of them. The side menu should put feature flags at the bottom so that they do not hide the other more important tags. How we can mitigate: Not much we can do. One option is prefixing all the feature flags with a character that makes them always be ordered last and easy to identify. Although this is not great and probably Sentry's biggest flaw, we believe the other benefits still make it worth it.
Product Area
Other