Unleash 5.2: Improved strategies and metrics
Here comes 5.2. The category is: Quality of life.
This comes with some pretty awesome new capabilities for Unleash strategies. Plus some useful tweaks to your user metrics.
Strategy Improvements
Unleash 5.2 lets you do a few more things with strategies: You can name them, you can turn them off and on, and you can set a default strategy per environment.
Let’s dive in.
Naming feature strategies
Names tell you what something is, and what something isn’t.
When you have multiple strategies in an environment, you might need a way to quickly describe what’s going on with a strategy beyond “gradual rollout.” Now you can.
Really this is a way to get information quickly and to keep your strategies organized within a single feature flag environment.
Enabling/disabling feature strategies
You can now treat entire strategies like feature flags. No, really.
For example, If you find yourself needing to temporarily remove a product, you no longer have to delete the strategy. Instead, you can just turn the strategy off.
This makes it easy to turn back on when you’re ready, instead of recreating the strategy from scratch. It’s not really that much different from a feature flag.
Configure default strategies
Before Unleash 5.2, a feature flag turned on with no strategies configured will have a gradual rollout of 100 percent.
This means you might turn it on for everyone in production, when you might have reasons to keep the initial rollout restricted.
You can now set up a default strategy in each of your environments in your project settings.
This is mostly meant as an additional safeguard against mistakes in, for example, testing environments.
Read more about our strategies in our fabulous documentation.
Usage metrics per variant
Metrics of your user activity will now show the percentage of each variant your users are exposed to.
You can see the data in a summary popup towards the right of the screen.
This will help you track the approximate percentage of users you’ve set for each variant. You can then match it to your own impression data to better understand the context.
What does Unleash do with this data? Nothing, actually. We don’t even touch it.
Unleash won’t see any user context associated with the new breakdown of exposed variants. This comes from Unleash being built with privacy by design.
More about Unleash metrics in our pretty sweet documentation. You can also read up on Unleash’s approach to privacy.
And that’s Unleash 5.2! Simple, flexible, and private, just how we like it.
