Skip to content
← Help center

Getting started

Find the trace behind an inference request

Production guidance · Console v0.2 · Updated

Open the correct project

In Console v0.2.2 with the current layout, select the organisation and project that received the inference request, then open Traces in the sidebar. A request attributed to another project or workspace will not appear in this view.

Narrow the results

Use All or Failed, Tag, Model, Key, Time window, and search to find the request. Tags should describe the workflow; avoid sensitive customer information in a tag. Open a row to inspect its status, model, captured content, timing, and usage.

Check that the payload was captured

A completed trace can contain only a metering record. If it says request and response payloads were not captured, it proves accounting activity but does not supply a replayable conversation. Do not use that placeholder as an evaluation prompt. Capture real input/output and verify it before collecting the case.

Connect a trace to evaluation data

Open Lab → Datasets to collect a tag/date cohort, or select the cohort in Lab → New evaluation. Inspect usable cases and cleaning state; a matching-trace count can include metering-only events. Save the exact dataset or snapshot used by a comparison. Read Evaluate and review for the full workflow.

If you cannot find the request

  • Confirm the API key's workspace and the application's project attribution.
  • Check the time window and tag filters before assuming an empty list means a service failure.
  • Record the request time, environment, and error or trace ID before contacting support. Keep private payloads and keys out of the message.

Use the quickstart request to send a tagged request and find it in Traces.

Sources and scope

Reviewed against a verified production release. The release record and source-code evidence are retained internally. Check the Console version and workspace availability in your environment.