OpenTelemetry Tracing for DeepSeek Harness

OpenTelemetry Tracing for DeepSeek Harness: A Complete Setup Guide

OpenTelemetry tracing for DeepSeek Harness lets you export every agent session, LLM call, and tool invocation as a standard OTLP trace tree to backends like Jaeger, Grafana Tempo, SigNoz, or Langfuse. You add it by installing a community plugin that implements the official @deepseek-ai/dsh-session-telemetry seam, configure an OTLP endpoint and a privacy mode, and then read the GenAI trace tree to debug agent loops, retries, and token usage. What is DeepSeek Harness and why it needs tracing DeepSeek Harness is the official open-source agent framework from DeepSeek, written in TypeScript with the tagline “Everything is a Plugin.” Its official repository has roughly 123,000 GitHub stars, making it one of the most popular agent harnesses in the ecosystem. The framework orchestrates multi-step agent loops: it plans, calls LLMs, invokes tools, spawns subagents, and retries failed steps. Each of those steps is a potential failure point, and without tracing you are effectively debugging a black box. ...

August 16, 2026 · 8 min · baeseokjae
AI Agent Observability with OpenTelemetry: From Dev to Production in 2026

AI Agent Observability with OpenTelemetry: From Dev to Production in 2026

OpenTelemetry is the standard way to add structured tracing, metrics, and logs to AI agents in 2026 — covering token usage, tool call latency, and multi-agent context propagation with a single SDK and vendor-neutral backends. Why Traditional Observability Fails for AI Agents Traditional APM tools like Datadog APM or New Relic were designed for deterministic request/response cycles: a user hits an endpoint, a function runs, a database query fires, a response returns. The execution path is fixed, latency is bounded, and errors are binary. AI agents break every one of these assumptions. An agent reasoning chain is non-deterministic — the same input prompt can trigger three tool calls in one run and seven in the next. Execution duration ranges from 500ms for a fast LLM call to 3+ minutes for a multi-step agent that searches the web, queries a database, and synthesizes results. Without agent-native spans, you cannot tell which tool call caused a timeout or why a particular run cost $0.40 while a similar one cost $0.03. Traditional APM measures function latency in microseconds and ignores tokens entirely. The LLM observability platform market recognized this gap — growing to an estimated $2.69 billion in 2026 and projected to reach $9.26 billion by 2030 at a 36.2% CAGR. OpenTelemetry’s GenAI Semantic Conventions fill that gap with a purpose-built span model for LLM operations, agent reasoning loops, and tool executions that traditional APM never anticipated. ...

May 19, 2026 · 18 min · baeseokjae