Supercharging Observability with Feature Flagging
summary
Combines feature flags with Honeycomb observability to track a real rollout of service maps, instrumenting traces with a feature key so every user journey across ~30–45 services is visible, letting teams detect spikes of 500 errors and latency the moment a flag flips and instantly flip the emergency rollback. Describes progressive beta cohorts, measuring impact on a single “gold” customer eight times larger than others, and using traces + metrics to segment experiments, iterate on UX, and tie product, support and SRE decisions to concrete telemetry.
AI-written summary · about
chapters (10)
- 0:00Introduction to feature flagging
- 2:27Progressive deployment and risk mitigation
- 4:14Deploying vs releasing features
- 7:00Observability in complex systems
- 11:13Real-world feature flagging example
- 17:19Customer adoption and feedback loops
- 21:37SRE role in observability
- 23:43Sales and business impact
- 25:32Summary and team collaboration
- 26:58Q&A session
related talks
29mCooking up o11y w/ Feature Flagging
23mFrom “What Broke?” To “What Changed?”: Unlocking Feature Flag Observability
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
44mObservability: Superpowers for Developers
50mObservability and the Development Process
39mFun with Flags: How OpenFeature Solves Your Feature Flag Heada...
31mObservability for Developers: How to Get There
27mOptimizing price performance with feature management and observability (PRT259)