Console
Logs
Every request that reached the Gateway, newest first, with the whole trace row behind each line.
/dashboard/logs is the request log. One row per call that reached the Gateway — the time, what was asked for, what served it, tokens, cost and status — and clicking a row opens the receipt the trace stored for it. Newest first, fifty rows a read, with a Load 50 older button underneath.
It is the same ledger the rest of the Console reads. Overview shows the newest ten of these rows and Usage totals them, so a figure that differs between the three is a bug rather than a different definition.
Filters
Four, and each one is a query rather than a client-side sift, so a filter applies to the whole period and not to the page you happen to have loaded. All four live in the URL: “the 5xx on the production key, last 30 days” is a link you can paste into a thread.
| Filter | Options | Use it for |
|---|---|---|
| API key | Any key on the org by name, or No key · session | Which client caused this. A row with no key was a browser session or a legacy runtime token. |
| Model | Every model that appears in the window, asked for or served | One model's failures, or checking where the router actually sent things. |
| Status | All, Succeeded, Failed, 4xx · caller, 5xx · us | The distinction that matters in a postmortem: whose fault it was. |
| Period | 7, 14, 30 or 90 days | How far back the query reaches. |
The receipt behind a row
Expanding a row shows every field the trace stores, in five groups, and nothing that is derived or estimated. A failed request puts its status, error class, error code and the provider’s own message at the top, with one line saying whose fault the class implies.
| Group | Fields |
|---|---|
| Request | Request id, exact timestamp, endpoint, streamed or buffered, client |
| Routing | Requested model, served model, whether the router changed it, provider, mode |
| Cost and size | Prompt, completion and total tokens, and the cost frozen at request time |
| Latency | Total round trip, and time to first token on a stream |
| Attributed to | The API key, and the legacy runtime row if the call came through one |
The request id is the value that came back in x-lobstack-request-id on that call, which makes a support thread a lookup rather than an interview.
—, and a banner above the table counts how many of the rows listed are in that state. It means the meter could not price the call — usually a model key the registry does not know — not that the call was free. The same rule runs through the ledger, the headers and the stream frame: Metering & cost.No savings figure appears here
Deliberately. The trace table records what a call cost and not what it was measured against, so it cannot tell a named baseline — you asked for a model and we served a cheaper one — from a plan_ceiling one, where you sent auto and the comparison is the dearest model your plan allows. Those are different claims, and subtracting two numbers here would present the flattering one as the other. The priced ledger carries the reason, and the response carries it on the call itself.