OTLP
The standard telemetry transport protocol defined by OpenTelemetry, used to transmit traces, metrics and logs between SDKs, the Collector and backends.
Core Facts
Timeline (last 90 days)
The OTLP protocol choice affects only the transport layer, not data semantics, so switching between gRPC and HTTP carriage does not change metric names or labels.
Claude Code has the OTel SDK built in, so the data format it outputs is not proprietary, and any OTLP-compatible backend (such as Prometheus, Datadog, Honeycomb, etc.) can receive it directly.
In production environments, an OpenTelemetry Collector typically receives OTLP data and then routes it to different backends according to configuration, so the application side only needs to program against OTLP and need not be tied to a specific vendor.
The Console destination can be regarded as a debugging alternative to the OTLP exporter: it makes no network requests and instead prints span data to standard output.
OTLP/HTTP sends telemetry data via standard HTTP requests, and the default port is usually 4318.
Agents with non-built-in runtimes can be instrumented and connected to Agent Observatory by sending OTLP/HTTP telemetry data, or by using the project-provided Python and JavaScript clients.
OTLP (OpenTelemetry Protocol) defines the standard communication format between collectors and backends.
n8n traces can be exported to any OTLP-compatible collector and backend, and the officially listed supported targets include Jaeger, Tempo, Datadog, Honeycomb, New Relic, and Grafana Cloud.
AI网关通常充当反向代理或SDK包装器，其数据流大致为：网关接收入站HTTP请求并创建根span，随后为具体操作创建子span（如`retrieval.search`、`llm.inference`、`llm.generate`），span通过OTLP批量导出到collector，再路由到Jaeger或Tempo进行存储与可视化。
OpenTelemetry (OTel) is a vendor-neutral observability standard covering three types of signals—distributed tracing, metrics, and logs—and defines how data is collected, propagated, and exported.
4 more timeline events
All Facts (15)
OpenTelemetry (OTel) is a vendor-neutral observability standard covering three types of signals—distributed tracing, metrics, and logs—and defines how data is collected, propagated, and exported.
65%UnverifiedOpenTelemetry defines a unified API, SDK, and data protocol OTLP, enabling developers to instrument once and export to multiple backends.
60%UnverifiedThe OTLP protocol choice affects only the transport layer, not data semantics, so switching between gRPC and HTTP carriage does not change metric names or labels.
50%UnverifiedClaude Code has the OTel SDK built in, so the data format it outputs is not proprietary, and any OTLP-compatible backend (such as Prometheus, Datadog, Honeycomb, etc.) can receive it directly.
50%UnverifiedIn production environments, an OpenTelemetry Collector typically receives OTLP data and then routes it to different backends according to configuration, so the application side only needs to program against OTLP and need not be tied to a specific vendor.
50%UnverifiedThe Console destination can be regarded as a debugging alternative to the OTLP exporter: it makes no network requests and instead prints span data to standard output.
50%UnverifiedAgents with non-built-in runtimes can be instrumented and connected to Agent Observatory by sending OTLP/HTTP telemetry data, or by using the project-provided Python and JavaScript clients.
50%UnverifiedOTLP/HTTP sends telemetry data via standard HTTP requests, and the default port is usually 4318.
50%Unverifiedn8n traces can be exported to any OTLP-compatible collector and backend, and the officially listed supported targets include Jaeger, Tempo, Datadog, Honeycomb, New Relic, and Grafana Cloud.
50%UnverifiedOTLP (OpenTelemetry Protocol) defines the standard communication format between collectors and backends.
50%UnverifiedAI网关通常充当反向代理或SDK包装器，其数据流大致为：网关接收入站HTTP请求并创建根span，随后为具体操作创建子span（如`retrieval.search`、`llm.inference`、`llm.generate`），span通过OTLP批量导出到collector，再路由到Jaeger或Tempo进行存储与可视化。
50%UnverifiedRootprint supports OTLP and HTTP NDJSON data ingestion, and can also pull data from Kafka, Kinesis, and SQS/S3.
50%UnverifiedMainstream observability backends including Jaeger, Grafana Tempo, Datadog, New Relic, and Elastic all support direct ingestion via the OTLP protocol.
50%UnverifiedOTLP supports two transport methods—gRPC and HTTP/protobuf—and is capable of carrying all three signal types: Traces, Metrics, and Logs simultaneously.
50%UnverifiedOTLP（OpenTelemetry Protocol）是CNCF主导的开放遥测标准，统一了追踪、指标和日志的数据格式与传输协议
50%