Find faulty features before your customers do
One of the most common reasons, our customers tell us, for moving towards feature flags is risk mitigation: the need to make sure releases don’t cause errors for users. Given how frequently organizations are now deploying features, the ability to limit the blast radius of a faulty feature becomes paramount. We found that not only do our customers want early insights into what could go wrong, but should it go wrong, they want to be able to respond to it within minutes.
One of the biggest successes we’ve had at Split in terms of customer feedback has been our ability to uniquely tie data to features. Showing different variants of a feature to different users means that every feature becomes an experiment. Tying each variant of the feature to user event data means that our customers can have early insights into the success of a feature. This in turn means greater confidence in rolling out the variant of a feature with the greatest likelihood of improving customer experience.
Tying data to features allows our customers to delight their customers better. Recently we asked ourselves what other data and functionality could enable our customers to serve their customers even better.
Introducing Feature Monitoring
To that end, we are very excited to announce the general availability of Feature Monitoring. We’ve built Feature Monitoring to automatically detect issues in releases caused by a recent change, determine the feature at fault, alert the right team, and switch off the feature instantly.
For example, if your page load times get worse or your error rates rise, even for just 5% of your users, as a result of recent change, Feature Monitoring can help you find the feature at fault before your customers do. Speaking more broadly, that means fewer rollbacks or hotfixes and greater confidence to move fast without breaking things.
We are very excited to demonstrate Feature Monitoring in greater detail. Watch this space for more blog posts on each of the key features. In the meantime, here are four things you can do to go deeper today:
- Watch a one-minute video covering the three key benefits of Feature Monitoring:
- Check out our help docs to get started (Sentry integration and RUM agent).
- Join the team that built Feature Monitoring in a webinar on September 24th.
- If you don’t have a Split account yet, sign up here and we’ll get you set up!
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.
Split manages more than 50 billion feature flags changes around the world every day. A recent study shows that about 5 to 6% of feature flags are rolled-back (or killed, using Split terminology in reference to a kill switch) within 30 days of being created. This speaks to the importance…
At Split we believe in the power of metrics, and are always striving to improve the ways we help our users make more data-driven product decisions. In this previous post we talked about the importance of understanding the impact of a new feature release via key and guardrail metrics. With…
When we speak to our customers, one of the most common reasons they say they made the move towards feature flags was the need to make sure their releases didn’t cause more errors for their users. By leveraging feature flags to ramp the release of their features to just small…