Usage Statistics
Definition
Open Admin → Insights → Usage Statistics to inspect recorded workspace consumption. Read measurement quantities, processing status and credit information according to their own displayed meanings.
Fields, states, or lifecycle rules
- Date filtering uses local calendar boundaries while timestamps are transported in UTC.
- Different measurements retain their own units.
- Recorded quantities are not charges.
- Processing status covers the workspace independently of the selected date range.
- A failed processing-status read does not remove the recorded quantity summary.
- Missing observations do not become zero use.
Read the summary
Choose the intended date range and compare like measurements. Tokens, execution time and other quantities cannot be added into one meaningful total simply because they share a table.
A recorded usage summary describes what has been ingested by that point. Pending or provisional processing can explain why more information may arrive. It is not proof that every provider event has already settled.
Inspect the ledger
Use available ledger details to connect a quantity or credit entry to its recorded activity and unit. Retain the actual currency and unit identities when exporting or explaining a value.
Credit displays have their own status and context. They do not turn a usage quantity into an invoice or establish a new spending guarantee. Follow your agreement for contractual billing questions.
Resolve unavailable information
Read the visible summary and processing state independently. A failed status request can coexist with a valid quantity summary. Use the provided refresh control for an unavailable read while preserving the selected date range.
Do not infer a charge, free execution or completed processing from an absent field. The screen reports recorded values and their availability.