One screen, scoped to who you are
Usage Telemetry is the single monitoring surface. It is reached from the Reports section of the Admin Console, and it presents the same shell to everybody while scoping the data entirely on the server.
| You are | What you see |
|---|---|
| Enterprise administrator | All workspaces by default, with a selector to narrow to one. Enterprise-wide commercial facts stay visible whichever workspace you pick |
| Workspace administrator | Your workspace. No enterprise-wide commercial facts, ever. If you administer several and have not picked one, you are asked to choose rather than given a silent first guess |
| Member | Your own activity, within your active workspace |
When telemetry is unavailable for the deployment, MSOCK says so explicitly instead of presenting empty metrics as zero activity.
Overview
The Overview tab leads with CKU Consumption for the current billing period, set against the allocation where one has been resolved.
Beneath it sit the time, cost, and quality indicators, including:
| Indicator | What it says |
|---|---|
| Evidence grounding | How much of what was produced is backed by evidence |
| Participation rate | How much of the population is actually using the product |
| Repeat usage | Whether people come back |
Adoption and usage
Three numbered sections:
| Section | What it holds |
|---|---|
| People & Devices | Active people in the window, with name, user, role, event count, and last-active time |
| SOCK Build Activity | What was built, and the model usage behind it |
| SOCI Workflow Activity | Lifecycle command activity |
Model Usage under SOCK Build Activity breaks down turns, priced and unpriced turns, input and output, cache writes and reads, observed cost, and cached share.
### Cost and token estimates
The SOCK cost display breaks usage down by processing phase and shows token counts and observed cost. Treat the total as an estimate, not an invoice. A turn can remain unpriced when it mixes models, uses an unknown model-and-speed pair, names a model absent from the pricing table, carries no model identity, or has an unknown cache duration. Where MSOCK has direct Claude billing evidence, the display identifies that basis.
An unpriced turn still contributes to token and activity counts where those measurements exist; it is not silently assigned a zero cost.
Subscription and capacity
| Group | Fields |
|---|---|
| Plan & Subscription | State, commercial phase, plan, plan version and display name, plan band, validity, days remaining, renewal date |
| Licence | Synced, revoked, access tier, valid through |
| Billing period | Period, decision, CKU committed, CKU active or pending, CKU allocated, CKU utilisation |
A Workspace Breakdown table shows, per workspace, the number of harnesses, how many were published, query volume, participation, and CKU committed.
Workspace and harness drill-down
An extra tab, currently labelled Projects & Captures in the interface, drills into workspace and harness activity. It follows the workspace selected in the main view rather than staying fixed on "all". Here, capture is the older internal label for a SOCK harness.
What the availability labels mean
MSOCK distinguishes several kinds of "no number", because their remedies differ.
| Label | Meaning |
|---|---|
| Unavailable | The value could not be read |
| Not captured | Nothing recorded this, so there is nothing to show |
| Incomplete (capped) | A bounded read hit its cap. A capped total renders as "At least N", never as a confident exact figure |
| Metering off | Metering is not enabled, so the committed figure has no meaning |
| Allocation not yet resolved | No allocation has been determined for this period |
CKU in one line
CKU consumption is computed from a harness's committed knowledge graph as ⌈(qualified nodes + qualified relationships) ÷ 1000⌉. See graph, Review and CKU for the full rules and what qualifies.