Observability
Per-model consumption, requests and execution traces, in the organization and the workspace.
Observability answers two different questions: how much was consumed, and what happened in a specific execution.
The screen exists in both scopes, with the same features. The Organization one adds up every workspace; the Workspace one covers just one.
It replaced the old Usage Logs page in version 4.
Model usage
The first tab summarizes the chosen period in three numbers: Tokens, Cost and Requests.
Below them, the Consumption by model chart spreads that total over time. The selector beside it switches the metric between tokens and cost and lets you group by another dimension.
The legend on the right lists the models by consumption. Clicking one hides it from the chart, which helps when a dominant model flattens the scale of the others.
The models table
Under the chart, one row per model:
| Column | What it's for |
|---|---|
Requests | How many calls were made to that model. |
Tokens | Total volume consumed. |
Cost | The corresponding amount, calculated from the provider's prices. |
% of total | The model's share of the period's consumption. |
Few requests combined with many tokens usually points to long prompts or Agents with many attached Collections.
Period and export
The Choose the period selector sets the window for every number on the screen. The refresh button reloads without changing the period.
Export downloads the current view's data, for analysis outside the platform.
Traces
The second tab lists executions with Root trace, Status, Duration and Cost. The filters narrow by resource identifier, application and user.
A trace covers the whole execution: the model call, the Collection search when there was one, and every tool call.
It is how you answer what the Conversations screen can't: why the answer took so long, whether the MCP was actually called, how much that message cost.
Administrative roles have a shortcut in the top bar to the detailed tracing tool, outside the platform.
Which scope to use
Use the Organization one to understand the company's cost and trends; the Workspace one to investigate a team's behavior.
People with an organization role reach both; people with only a workspace role see only their own.