Improving your Sentry Debugging Experience with Insights into Feature Flags #73542
Replies: 1 comment
-
Snuba has its own runtime config that reads from redis. Knowing the feature flags that were toggled at what time could be good for sure
At this time I am switching between datadog for understanding infra load and sentry for business logic issues
Often, there's something in the sentry repo that is changed (by turning on a feature flag) that will cause a lot of downstream impacts on the infra. At the moment the way I debug them is go into #team-engineering and ask "yo what's going on, who broke this" |
Beta Was this translation helpful? Give feedback.
-
📄 Background
We, at Sentry, use feature flags regularly to change our application behaviour and appearance conveniently without deploying new code. For example, our development process includes slowly rolling out new features to ensure they don’t introduce new errors and collect early product feedback.
We know that feature flag changes are just as valuable and critical to the debugging process as are code releases for some organizations. As such, we're looking at enhancing our context to include insights on your feature flags and integrating with popular feature flag systems. For example, displaying flags evaluated at the time of an error event, in order, on our Issue Details page.
👋 We’d like to hear from you
Please share your initial thoughts and impressions below. 👇 If you’re interested in chatting live with the Sentry team on this topic, let us know below and we can schedule a call. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions