List view
# Overview Experimentation is a primary use case for feature flags. In practice, this often means flag variants are assigned to users at random or in accordance with a business rule, while the impact of the assigned variant on some business objective is measured. Vendors and custom solutions often support a _tracking_ or _goal measuring_ API to facilitate the measurement of these business objectives. OpenFeature should provide a equivalent API to facilitate this use case. ## Goals - Develop official terminology to support consistent implementation - Specify a flexible API widely compatible with basic vendor functionality - Define tracking event payload - Define tracking event identifier - Support client and server paradigms ## Non-goals - Creating an experimentation platform - Covering every user-tracking use case - Focus on A/B testing, and experimentation based on feature flags - Focus on "facts" not "metrics" - Simple point in time data, no aggregation We value the following: - Adherence to, and compatibility with OpenFeature semantics - Maximum compatibility and ease-of-adoption for existing solutions - Minimum traffic and payload size - Ease-of-use for application authors, integrators, and provider authors (in that order) If you are interested about the OpenFeature Tracking effort, you can join the #openfeature-tracking slack channel on the CNCF Slack.
No due dateBeta version of the OpenFeature specification
No due dateAlpha version of the OpenFeature specification
No due date•14/14 issues closed