> ## Documentation Index
> Fetch the complete documentation index at: https://to11.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Observe

> See what your LLM application is doing in production.

Once your application is [instrumented](/docs/instrument/overview), every LLM call lands in to11 as an OpenTelemetry-native trace. Observe is where you read that data back — to follow a single request, debug a failure, or understand how a multi-step workflow actually ran. Data is scoped to a project: pick a project, and you see its traces.

Today, Observe means traces. Aggregate metrics and pre-built dashboards build on the same data and are on the way.

## Traces

A trace is the full record of a request — every LLM call with its inputs and outputs, latency, tokens, and cost, plus any child calls nested under one trace for a multi-step workflow. The [Trace Explorer](/docs/observe/traces) lets you filter by time, provider, model, status, and more, then open any trace to inspect its spans in a waterfall view.

## Metrics and dashboards

<Info>
  Coming soon. Aggregate latency, token, error, and cost signals over your traces, plus pre-built dashboards for your golden signals.
</Info>

## Access

Who can view traces — and production traces in particular — is governed by your role. See [Roles & permissions](/docs/platform/roles-and-permissions).

## Next steps

<CardGroup cols={2}>
  <Card title="Traces" icon="magnifying-glass" href="/docs/observe/traces">
    Explore and filter individual requests.
  </Card>

  <Card title="Instrument" icon="plug" href="/docs/instrument/overview">
    Get your data flowing first.
  </Card>
</CardGroup>