Introducing Virtual MCP Servers
LogoLogo
GithubJoin SlackSignupBook a Demo
  • Documentation
  • Self Hosted
  • Integrations
  • Guides
  • Enterprise
  • Introduction to AI Gateway
  • Supported Models
  • Supported MCP Servers
  • Getting Started
    • Quick Start
    • Working with API
    • Working with Multiple Agents
    • Working with MCPs
    • Working with Headers
    • User Tracking
    • Using Parameters
  • Concepts
    • Thread
    • Trace
    • Run
    • Label
    • Message
    • Virtual Models
      • Routing with Virtual Model
    • Virtual MCP Servers
  • Features
    • Tracing
    • Routing
    • MCP Support
    • Publishing MCP Servers
    • Usage
    • Analytics
    • Guardrails
    • User Roles
    • Cost Control
  • Python SDK
    • Getting Started
  • API Reference
  • Postman Collection
Powered by GitBook
LogoLogo

Social

  • LinkedIn
  • X
  • Youtube
  • Github

Platform

  • Pricing
  • Documentation
  • Blog

Company

  • Home
  • About

Legal

  • Privacy Policy
  • Terms of Service

2025 LangDB. All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. Concepts

Trace

Track complete workflows with LangDB Traces. Get end-to-end visibility, multi-agent support, and error diagnosis.

PreviousThreadNextRun

Last updated 17 days ago

Was this helpful?

A Trace represents the complete lifecycle of a workflow, spanning all components and systems involved.

Core Features:

  • End-to-End Visibility: Tracks model calls, tools across the entire workflow.

  • Multi Agent Ready: Perfect for workflows that involve multiple services, APIs, or tools.

  • Error Diagnosis: Quickly identify bottlenecks, failures, or inefficiencies in complex workflows.

Parent-Trace:

For workflows with nested operations (e.g., a workflow that triggers multiple sub-workflows), LangDB introduces the concept of a Parent-Trace, which links the parent workflow to its dependent sub-workflows. This hierarchical structure ensures you can analyze workflows at both macro and micro levels.

Headers for Trace:

  • trace-id: Tracks the parent workflow.

  • parent-trace-id: Links sub-workflows to the main workflow for hierarchical tracing.

An example of Trace linked to a thread can look on LangDB