The Feature Flags and Session Recording can only check from the Usage

Feature request

Is your feature request related to a problem?

We need fine‑grained usage data for Feature Flags and Session Recording to analyze and optimize costs. Today the Usage view shows only overall totals, which makes it hard to identify hotspots, set budgets, or justify optimizations.

Please describe.
Current state: Flags and Session Recording usage are presented as aggregates (e.g., total evaluations, total recording hours) without drill‑downs.
Impact:

• Can’t see which specific flags drive the most evaluations/traffic.
• Can’t segment recording ingestion/storage by project, source (web/mobile), environment, or date.
• Hard to forecast billing, detect anomalies, or measure the effect of optimizations (e.g., sampling, archiving, disabling noisy flags).

Describe the solution you'd like

We can do the query to split detail for every features flag, available in the UI, HogQL, and via API export

Describe alternatives you've considered

For features flags: we're using $feature_flag_called as workaround, but we can't get exactly mapping with the current flags request billed

Additional context

• Identify top cost drivers (e.g., a flag evaluated on every request, long unviewed recordings).
• Set team‑level budgets and alerts.
• Validate the ROI of changes (e.g., caching flags, increasing sampling, deleting stale recordings)

Debug info

- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]