iGotLabs / Owner workspace
Operations
Usage, reliability, and the cost of serving your customers.
Connecting securely…
Needs attention
Reporting coverage
Feature activity
Users
All platform-linked users, including those without AI activity. Select a user for transactions and provider attempts. Usage and costs follow the report dates; subscription and spendable credits are current. Last activity is the latest recorded AI request or product action in the period, not a login. Product actions are collected from September 7; token totals are recorded usage, with gaps shown separately.
AI provider usage
Provider facts use completion/attempt dates. Legacy aggregates appear once; missing usage remains unknown. Customer credits are separate from provider expense.
API routes
Collection boundaries
Request metrics describe captured backend requests, not browser latency or uptime. Runtime probes measure this process and a SELECT 1 round trip; they do not establish health of Clerk, Stripe, AI providers or object storage. Missing samples remain gaps.
Daily performance baselines
Percentiles use captured request observations, never averages of percentiles. Delta compares the prior UTC day. Runtime coverage is minutes with at least one sample, not request completeness or per-replica coverage. Fewer than 100 requests is a low-sample warning.
Release observations
Process starts observed by this collector. A restart can repeat the same release; timestamps are not confirmed deployment times. History begins when collection is deployed.