Subscribe
Topic

OpenTelemetry

Using OpenTelemetry to trace and monitor LLM applications. Posts explain the OpenTelemetry GenAI semantic conventions and how they compare with OpenInference, and compare observability tools like Langfuse, Arize Phoenix and LangSmith.

Articles

1-3
  1. LLM Observability and Tracing in Production: Comparing Langfuse, Arize Phoenix, LangSmith, and OpenLLMetry

    Moving language models from single-turn prompt wrappers into multi-agent architectures, recursive Retrieval-Augmented Generation (RAG) graphs, and autonomous tool-calling loops fundamentally changes system dynamics. LLM applications behave as distributed state machines where failure modes are rarely deterministic. Latency spikes can stem from vector store indexing bottlenecks, context window bloat, or slow token generation, while quality degradations emerge through subtle prompt drift, context c

    AI
    7 min read
  2. LLM Observability in Production: OpenTelemetry GenAI Semantic Conventions vs. OpenInference, Distributed Trace Propagation Across Multi-Agent Graphs, and High-Throughput Sampling Economics

    Production large language model (LLM) architectures have transitioned from isolated completion endpoints to complex, distributed directed acyclic graphs (DAGs). Modern AI systems incorporate multi-agent orchestration, iterative tool execution, vector retrieval pipelines, and speculative decoding loops. Operating these workloads at enterprise scale exposes critical observability gaps that traditional application performance monitoring (APM) tools cannot address. Standard request-response APM metr

    AI
    7 min read
  3. LLM Observability in Production: OpenTelemetry Semantic Conventions, Distributed Tracing, and Latency Profiling

    LLM Observability in Production: OpenTelemetry Semantic Conventions, Distributed Tracing, and Latency Profiling Deploying large language models into production introduces failure modes that traditional application performance monitoring (APM) tools were never designed to diagnose. Standard web services fail with discrete HTTP error codes, predictable database timeouts, or memory leaks. In contrast, LLM applications fail through silent semantic drift, hallucinated tool parameters, unbounded prom

    AI
    6 min read