Tracing Servers

Connect observability and monitoring for agent execution

Tracing Servers provide observability into agent execution and performance.

What are Tracing Servers?

Tracing servers collect telemetry data from agent execution:

  • Traces - End-to-end request flows
  • Spans - Individual operation timing
  • Logs - Structured event data
  • Metrics - Performance statistics

Why Tracing?

Understanding agent behavior is critical for:

  • Debugging - Find why an agent failed
  • Performance - Identify slow operations
  • Cost - Track token usage
  • Compliance - Audit agent decisions

Supported Platforms

Langfuse

Open-source LLM observability platform:

  • Trace visualization
  • Cost tracking
  • Prompt management
  • Evaluation metrics

OpenTelemetry (Soon)

Standard observability protocol:

  • Vendor-agnostic
  • Wide ecosystem support

What Gets Traced

EventData Captured
Agent TurnInput, output, duration, tokens
Tool CallTool name, args, result, timing
Memory SearchQuery, results, relevance
Context BuildTemplate, data, token count

Configuration

Connect your tracing server in team settings:

  1. Add tracing server connection
  2. Provide API key and endpoint
  3. Select which teams to trace
  4. View traces in your observability platform

On this page