# Get traces out of an agent framework into a backend

> Get traces out of an agent framework into a backend: 5 companies fully do it, 11 with a limit, 22 carry the tag. Every listing in Agent observability & evals with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-observability.instrument-app/
- Markdown: https://www.anchorterminal.com/niches/agent-observability.instrument-app/index.md (~2,100 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-observability.instrument-app/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-observability.instrument-app/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 5 | 11 | 22 | 17 | 19 |

## What counts as done

Spans arrive under one trace per request with the framework's model and tool steps as children, and no root span is lost under async.

Measured, for our own tests: setup takes under 30 lines, and a test request is visible within 5 minutes of starting.

How agents ask for it: add tracing to my LangGraph agent; send OpenTelemetry spans to it; keep FastAPI and the agent in one trace; why is my root span missing

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Arize Phoenix (Arize AI, Inc.)**: OTLP over gRPC or HTTP, phoenix.otel register, OpenInference instrumentors for LangGraph, ADK, Pydantic AI and others, and a context propagation page covering asyncio and threads. An HN self-hoster had no tracing complaints.
- **Laminar API + MCP (LMNR AI, Inc.)**: OTLP over gRPC, HTTP protobuf and HTTP JSON on documented ports for cloud and self-hosted, OpenLLMetry conventions, integrations for LangChain, Vercel AI and the Claude Agent SDK; ingest answers 400, 401 and 413 and flush_by_size avoids oversized batches.
- **LangWatch (Reasoning Engine B.V. (doing business as LangWatch))**: OTLP at /api/otel/v1/traces with a project key, Python, TypeScript and Go SDKs, a LangGraph node-by-node page and semantic conventions tutorial; gateway traffic emits traces automatically. Cost enrichment runs in the same pipeline.
- **Pydantic Logfire (Pydantic Services Inc.)**: OTel-native: any OTLP exporter posts to logfire-us or logfire-eu with a write token, FastAPI and Pydantic AI instrument in one line and spans appear within seconds; two HN users found Pydantic AI plus Logfire the easiest agent debugging.
- **Respan API + MCP (Keywords AI Inc. (d/b/a Respan))**: OTLP/HTTP in JSON or protobuf at /api/v2/traces with a Bearer key, gen_ai attributes shown, plus an SDK that auto-instruments OpenAI, Anthropic, Bedrock and Vertex and integration pages for LangGraph, ADK, Pydantic AI and Vercel AI.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **BotGauge (BotGauge AI Inc. (Delaware, United States))**: OTLP/HTTP protobuf at api.botgauge.com/v1/traces with a Bearer key from the SDK or any exporter, integrations for LangGraph, ADK, OpenAI Agents and Pydantic AI. Bare exporters get no session ids or masking, and the service excludes the EEA and UK.
- **Braintrust API + MCP (Braintrust Data, Inc.)**: OTLP at api.braintrust.dev/otel with x-bt-parent and documented gen_ai and OpenInference attribute mapping, plus framework pages for LangGraph, ADK, Pydantic AI and Vercel AI. wrapAISDK produced nested duplicate spans (992) and a logged span exposed the API key (912).
- **Galileo API + MCP (Galileo Technologies, Inc.)**: GalileoSpanProcessor exports OTLP to api.galileo.ai/otel/traces with OpenInference instrumentors for ADK, Pydantic AI and Vercel AI, and traceparent joins distributed spans. The ADK example warns about asyncio context cleanup, and self-hosted endpoints differ.
- **Helicone AI Gateway + MCP (Helicone, Inc.)**: Traces arrive by changing the base URL to the gateway or through the OpenLLMetry async integration; framework pages cover LangGraph, OpenAI Agents and Vercel AI. No general OTLP endpoint is documented, so non-model steps need session headers.
- **HoneyHive (HoneyHive Inc.)**: The SDK wraps an OTel TracerProvider, accepts OpenInference and OpenLLMetry instrumentors, and propagates W3C context across services. A raw OTLP exporter without the SDK is available only by contacting HoneyHive.
- **Langfuse API + MCP (Langfuse GmbH (a ClickHouse, Inc. company))**: OTLP endpoint /api/public/otel plus OTel-native SDKs and framework pages for LangGraph, ADK, Pydantic AI and Vercel AI. Root traces went missing under FastAPI plus LangGraph (issue 13023) and most traces vanished at sampling 1.0 (issue 8837).
- **LangSmith API + MCP (LangChain, Inc.)**: OTLP at the API URL plus /otel with x-api-key and a Langsmith-Project or agent headers, and integration pages for LangGraph, ADK, Pydantic AI and Vercel AI. Trace context did not reach the app's own OTel spans (SDK issue 58) and Python below 3.11 splits async traces.
- **MLflow Tracing (MLflow Project, a Series of LF Projects, LLC)**: OTLP at /v1/traces with an x-mlflow-experiment-id header, GenAI semantic conventions, a FastAPI example and W3C traceparent propagation. Threads need contextvars copied, expired credentials drop traces with only a log line, and autolog regressed for Pydantic AI (22208).
- **Opik API + MCP (Comet ML, Inc.)**: OTLP at /api/v1/private/otel with projectName and Comet-Workspace headers, mapping GenAI, OpenInference and Opik attributes; SDK batching and an offline fallback that replays failed messages. Streamed ADK spans never finalised (5524).
- **Overmind (Overmind Technology Ltd (England and Wales, company 16585996))**: OTLP protobuf or JSON at /api/v1/traces with X-Api-Key, normalising GenAI, OpenLLMetry and OpenInference attributes; the Python SDK instruments OpenAI, Anthropic, Google, Agno and LangChain or LangGraph and warns against competing TracerProviders. Alpha SDK.
- **W&B Weave (Weights and Biases, LLC)**: OTLP protobuf to /agents/otel/v1/traces with wandb-api-key and GenAI conventions, no SDK needed. Spans without entity and project are dropped, a doubled path yields a 404 and silently dropped spans, and the docs now point new agent users to Agent Lens.

- not this job: Agent Tree (No legal entity found. The LICENSE, plugin.json and marketplace.json name "Mike Pollow, Digitalroots"): A Claude Code plugin, not a backend.
- not this job: agents-tree (No legal entity found. The LICENSE and pyproject.toml name Karel Blavka): A CLI that reads transcripts, not a backend.
- not this job: DeepEval (Confident AI, Inc.): Tracing is for attaching metrics to spans during evaluation, not a backend that ingests production traces.
- not this job: Gauge CLI (Gauge): Nothing to instrument; Gauge runs Claude Code, Codex, OpenCode, Pi or Antigravity in Docker or hosted VMs.
- not this job: Navige (Navige Ltd): A proxy with no OTLP ingest; traceparent is read only to correlate calls into a transaction.
- not this job: Prefactor (Prefactor Pty Ltd): The full documentation never mentions OpenTelemetry or OTLP; spans come only from the TypeScript and Python SDKs against your own activity schema.

## What stops agents finishing

- framework not in the integration list and no OTLP endpoint
- OTel context conflict with the framework's own instrumentation
- traces stop after an SDK or platform upgrade
- no way to point the SDK at another backend
- agent reachable only over HTTP with no instrumentation inside

## Around it

Before: agent-harnesses.embed-in-program, inference.tool-loop. After: agent-observability.debug-failed-run, agent-observability.cost-per-run.

## Where this comes from

Weight 17 of 100 in Agent observability & evals: 19 of 86 accounts: Langfuse issues on async root spans, trace_context, callback handlers and sampling; Logfire, Weave, Opik, Braintrust and LangSmith SDK issues on integrations, context propagation, exporters, dependencies and leaked keys; Phoenix issues on black-box agents and dropped spans; the LangChain forum outage thread

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-observability.instrument-app.json, or the MCP tool get_use_case with id agent-observability.instrument-app. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
