Evaluation Activity

Every time one of your applications evaluates a config, the SDK reports it back to ConfigDirector. The dashboard turns those reports into per-config activity for each environment, so you can confirm that a rollout is doing what you expect, see which value your users are actually getting, and find configs that nothing evaluates anymore.

Activity is available in all of our plans and needs no setup beyond using an SDK.

What is recorded

For each evaluation the SDK reports:

• The config key and the environment, taken from the SDK key in use.
• The value that was served.
• Whether the application fell back to its in-code default value instead, and why (for example the config was not found, or it was requested as an incompatible type).
• The SDK name and version.
• The identifier of the context the value was evaluated for, when the application provided one.

Client SDKs report evaluations in batches shortly after they happen. Server SDKs evaluate targeting rules locally and report aggregated counts periodically. In both cases the activity appears in the dashboard within moments of the report arriving, usually well under a minute after the evaluation.

Evaluations of keys that do not exist in the project are recorded separately. They never appear in a config's activity, because there is no config to attach them to, but they do raise a Config not found alert.

The Activity tab

Open a config and select the Activity tab. Pick the environment at the top left and a time window at the top right: the last 8 hours, 24 hours, 48 hours, 7 days, or 30 days. Times are shown in your local time zone.

Three charts are shown for the selected environment and window:

• Total Evaluations: how many times the config was evaluated over time. Use it to confirm an application is live in an environment, to see traffic patterns, and to notice when evaluations stop.
• Evaluations by Value: the same evaluations broken down by the value that was served. During a percentage rollout this is where you check that the split matches the percentages you configured. After a rollout reaches everyone, one value should account for all of the evaluations.
• Evaluations by SDK: the evaluations broken down by SDK name and version. Use it to see which applications have picked up a change, and which are still running an older SDK.

Activity in the configs list

The configs list shows an Evaluations (last 7 days) column for the selected environment, with a small chart and the total for the week, next to the config's lifecycle state. A config that shows "No evaluations" in every environment is a candidate for cleanup, and the lifecycle states track exactly that.

Last evaluated

When you archive a config or change its SDK availability, the confirmation dialog shows when the config was last evaluated in each environment and through which SDK key, so you can see whether anything still depends on it before you go ahead.

The same information is available to AI coding tools through the MCP server's get_config_activity tool.

Activity per context

Contexts that your applications identify with an id appear on the Contexts page for their environment. Open a context to see which configs were evaluated for it in a time window, and which value each one returned. This is the quickest way to answer "what did this user get" when someone reports that a feature looks different for them than expected.

Retention

The longest activity window available is 30 days, and the charts always have the full history they can display.

Archiving a config removes its activity along with it. If you need the numbers, take them from the Activity tab before archiving.