When flagging systems begin to scale, things can get messy fast. Imagine multiple team members editing the same flag over the course of a project, but then something goes wrong. Thanks to the risk mitigation provided by your flagging system there isn’t much damage done, but what about accountability? In order to identify the last change made to a flag, you require an audit log. More than just a list of events, a true audit log provides information on the who, what, when, and why of flag changes. This is a feature that is often left out of homegrown systems, despite its importance at scale.
In the full article, here, Kim Harrison of LaunchDarkly discusses this important best practice of feature management.