Cooking up o11y w/ Feature Flagging
summary
Combining feature flags with observability yields live technical and business signals: Honeycomb traces, OpenTelemetry attributes and Jaeger-style spans tie a service maps rollout to user IDs and latencies so teams see duration in ms, SLO violations, and who’s affected. A service-maps experiment runs behind a feature-flagged exclusive preview for three enterprise customers plus one niche customer, producing actionable data that changes the roadmap, exposes a bad looping contractor change, and lets teams flip a flag to rollback and cut MTTR.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 1:07What are feature flags
- 3:39Mitigating risk with flags
- 5:04What is observability
- 7:54Business context in traces
- 10:46Error monitoring and recovery
- 12:13Rollbacks and quick fixes
- 12:56The Supercharged team story
- 15:22Power of synergy in teams
- 17:05Product manager’s role
- 18:28Customer adoption insights
- 19:33Consistent feedback loops
- 20:36SRE and observability
- 23:01Support team’s technical role
- 25:07Sales influence on growth
- 26:31Summary and team collaboration
related talks
33mSupercharging Observability with Feature Flagging
23mFrom “What Broke?” To “What Changed?”: Unlocking Feature Flag Observability
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
39mFun with Flags: How OpenFeature Solves Your Feature Flag Heada...
44mObservability: Superpowers for Developers
31mObservability for Developers: How to Get There
50mObservability and the Development Process
27mOptimizing price performance with feature management and observability (PRT259)