Project insights
Interpret hosted traffic, errors, operational signals, and per-flag totals accurately.
Project Insights is a read-only operational surface built from privacy-safe hosted aggregates. Use it to find configuration and runtime work, not as product experimentation analytics.
Insights covers requests that reach FeatureGate's hosted runtime API. Local Node.js snapshot evaluations remain inside the application and are not counted as exposures.
Select a 7-, 14-, or 30-day range. Add an environment filter when production traffic, staging tests, and development activity would otherwise obscure each other.
Start broad when looking for project-wide change. Narrow to one environment when diagnosing an incident, rollout, or rate-limit pattern.
The selected range changes aggregation context. It does not recover raw requests or evaluation values.
Insights can summarize:
Use rate-limit and error trends before blaming a targeting rule for an application change. A drop in requests may be deployment traffic, credential failure, or migration to local snapshot evaluation.
Action-first signals can lead to kill-switch state, fallback review, stale lifecycle work, or an environment that needs configuration.
Follow the link to the owning resource and validate current state. A signal is a prompt for review, not an automatic diagnosis or configuration change.
Projects with no flag, key, or first hosted request should use project activation and environment readiness. Insights is not the setup wizard for an inactive project.
Direct per-flag totals count existing requested flags in hosted evaluation calls. They do not count:
A high total can represent repeated requests from a small population. A low total can coexist with substantial local SDK use.
Use application metrics, logs, traces, and business analytics to answer questions about user impact. Correlate through time windows, deployments, and privacy-safe request IDs.
Do not copy full context or resolved flag values into FeatureGate notes. Avoid logging them in the application merely to compensate for aggregate platform telemetry.
FeatureGate does not store raw context, user identifiers, targeting values, or resolved values in these aggregates. Insights is intentionally not a raw request explorer.
This protects callers but limits retrospective analysis. Design application observability before a high-risk rollout rather than expecting FeatureGate to reconstruct exposure later.
Related pages: Environment readiness, Run a controlled rollout, and Errors and fallbacks.