Feature flags
Release with a little more control.
Configure flags by environment, roll out gradually and compare cohort health to understand how a change behaves in use. Follow the evidence in your project.
Separate deployment from exposure
Use boolean flags to control a capability after deployment. Explicit targeting and percentage rollouts support a more gradual introduction.
Evaluate in your application
The .NET SDK evaluates locally from its cached configuration. Configure appropriate defaults so a feature can behave predictably when the service is unreachable.
Watch the exposed cohort
Compare error rates between flag cohorts where the relevant telemetry is available. A rollout control helps limit exposure, but does not replace testing or an operational rollback plan.
Related
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- Fix what matters to your users. Bring errors, performance and feature usage together to help prioritise engineering work by its effect on the product.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.