Tell the SDK what a flag evaluated to, and every event of the view carries it:
To follow a flag service, hand it the evaluations. LaunchDarkly has inspectors, and OpenFeature has hooks:
The feature flags tab
Feature flags lists the flags sessions evaluated in the range, the one most sessions met first. Choose one to compare its values side by side: sessions, the share of views with an error and with a sign of frustration, and for a browser application the 75th percentile of LCP, INP, and CLS. The value with the most views with an error is in red. See these views opens them in the explorer.
Ask of a flag anywhere
A flag is named like a column, as feature_flags.<key>, wherever the explorer and the API take a field:
The same goes for the other keys of a JSON column: context.<key>, usr.extra.<key>, and view.custom_timings.<key>. GET /api/v1/rum/keys lists the keys there are.
In SQL, read a key with json_text("feature_flags", 'checkout_v2'), which is text, or NULL for a key the row does not have. json_keys("feature_flags") lists the keys of a row.
Mole Agent
The tool get_rum_feature_flags lists the flags, and with flag compares its values with the same numbers. Last modified on October 31, 2026