docs(server): document kura_usage_events in data-export.md

Metadata

Source

tuist/tuist #10989

Updated

Jun 11, 2026

Domains

Kura

Details

Follow-up from #10979 (Cache usage dashboard).

That PR added the kura_usage_events ClickHouse table and the supporting Tuist.Kura.Usage ingest path, but did not update server/data-export.md so the data-export inventory stays complete for GDPR / CCPA exports.

What needs documenting

In the Analytics Data (ClickHouse) section of server/data-export.md, add:

Kura usage rollups (kura_usage_events table): per-hour usage rollups pushed by managed Kura nodes for the account. Columns:
- event_id — deterministic dedupe key
- account_id, project_id — Tuist identifiers (zero when the handle didn’t resolve at ingest)
- node_id, region — which cache node served the traffic
- traffic_plane, direction, operation, protocol, artifact_kind — classification
- bytes, request_count — metered totals
- window_start, window_seconds, inserted_at — window timing
- retention: same as other ingest_repo rollups (partitioned monthly on window_start)

Surface this under “Exportable Data” alongside the existing analytics tables.

Why a follow-up

Was kept out of #10979 at @pepicrft’s request to keep that PR scoped. Tracking it here so the export inventory doesn’t drift.

cc @fortmarek

Flights

Investigate, reproduce, or fix this item in an isolated repository. Each Flight preserves its outcome and agent session.

New Flights are paused Configure model inference, GitHub, and a sandbox provider to start another Flight. Existing results remain available below.

No Flights yet

Start a Flight and preserve its objective, outcome, and session here.

Comments

No GitHub comments yet.