GlossaryProductsIntermediate

OpenTelemetry traces

Also written: OTel traces

Records of how software actions flow through a system, used for debugging and performance monitoring.

In plain terms

OpenTelemetry traces are like a detailed travel log for a software request. When you ask an AI model a question, your request doesn't just go to one place. It might go through several different services or steps to get processed. A trace records every single step, showing where the request went, how long each step took, and what happened.

Think of it like tracking a package. The trace shows you when it was packed, when it left the warehouse, when it arrived at a sorting facility, and when it was delivered. For software, this helps developers understand if a request is slow because one specific step is taking too long, or if there's an error somewhere in the process.

The expert version

OpenTelemetry traces are a standardized way to represent the end-to-end journey of a request as it propagates through distributed systems. A trace is composed of spans, where each span represents a unit of work (like a function call or an API request) with a start time, duration, and associated metadata. Traces enable observability by providing detailed insights into request latency, error sources, and system behavior, crucial for debugging and performance optimization in complex microservice architectures.

Why it matters now

OpenTelemetry traces are becoming more relevant as frontier AI labs build increasingly complex, distributed systems. Understanding the flow of requests and operations through these systems, as captured by traces, is crucial for debugging, performance optimization, and ensuring the reliability of AI services.

Where it shows up 1 items, newest first
How each company uses it
Google Gemini
Google Gemini uses OpenTelemetry traces to monitor and understand the performance and behavior of its AI models and platforms, particularly in enterprise applications.
Related terms

OpenTelemetry metricsOpenTelemetry logsDistributed tracingObservabilityMicroservicesAPI monitoring

Often confused with
OpenTelemetry metrics
Metrics are aggregated numerical data over time, like req
OpenTelemetry logs
Logs are discrete events or messages, often text-based, prov
Request ID
A request ID is a unique identifier for a single request, but it doe
Origin

OpenTelemetry is an open-source observability framework, a CNCF project that evolved from the merging of OpenTracing and OpenCensus. It aims to standardize the generation and collection of telemetry data. Source ↗

Try this about 5 minutes

You can explore OpenTelemetry traces by using tools like Jaeger or Zipkin. If you are running a local application that has OpenTelemetry instrumentation, you can send traces to one of these backends and visualize the request flow. Look for a trace that shows a slow or failed request to understand how traces help pinpoint issues.

Try it: Playbook entries that use thisPlaybook →

The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.

Questions people ask

What is a span in OpenTelemetry?
A span represents a single operation or unit of work within a trace, such as an incoming HTTP request or a database query. It has a start time, duration, and can contain metadata.
How do traces help with performance?
Traces show the latency of each step in a request's journey. By visualizing this, developers can identify bottlenecks and optimize slow parts of the system.

First seen on Subvolts Sep 16, 2026. Updated Sep 22, 2026. Written by an AI model from the items above and reviewed against them weekly; report an error.