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

# Tracing

Tracing records what your agent does (LLM calls, tool use, and control flow) so you can debug individual runs and understand behavior over time.

Tracing is also the entry point into Laminar: it’s how production runs become data in the platform. Once you’re tracing, you can read each run as a transcript in the [trace view](/platform/viewing-traces), define [Signals](/signals) to extract outcomes and failures across traces, and replay runs in the [Debugger](/debugger/introduction) to reproduce and fix what went wrong. From there, turn real failures into [Datasets](/datasets) and run comprehensive [Evaluations](/evaluations).

<Frame caption="Trace view with the transcript and extracted signals">
  <img src="https://mintcdn.com/laminarai/OhGMtzTFdQqw5xso/images/trace-screenshot.png?fit=max&auto=format&n=OhGMtzTFdQqw5xso&q=85&s=7d5b5f31e2968039160a52a6418cca6f" alt="Laminar trace view showing the traces list, transcript view, and an extracted signal" width="1613" height="1052" data-path="images/trace-screenshot.png" />
</Frame>

## Where to Start

<CardGroup cols={2}>
  <Card title="Integrations" href="/tracing/integrations/overview">
    You’re already using supported libraries. Learn what’s captured and how to configure instrumentation (including Browser Use and Stagehand).
  </Card>

  <Card title="Tracing Structure" href="/tracing/structure/overview">
    You want deeper visibility into your own code. Trace your functions, create manual spans, add context, and control what’s captured.
  </Card>

  <Card title="Troubleshooting" href="/tracing/troubleshooting">
    You’re not seeing what you expect. Debug missing spans, auto-instrumentation issues, and common setup pitfalls.
  </Card>
</CardGroup>