Protocols
Saved & recent

OTLP

Also called: OpenTelemetry Protocol, OTLP/gRPC, OTLP/HTTP

OpenTelemetry Protocol transports telemetry between applications, collectors, and backend services. It defines export requests, responses, and data schemas for signals such as traces, metrics, and logs. Its gRPC and HTTP variants carry the same kinds of telemetry through different protocol bindings; the HTTP variant supports binary or JSON Protocol Buffers encoding.

For example, a checkout service can export a batch of trace spans to a collector, which forwards them onward. The collector’s acknowledgment concerns that hop, not guaranteed final storage across the entire pipeline. Export responses can report partial acceptance, and retry rules distinguish temporary failures from data that should not be resent unchanged.

Read first
gRPC
Related
gRPC, Protocol Buffers, Syslog, Retry backoff and jitter
Further reading
OpenTelemetry — OTLP Specification 1.11.1
application collector backend Export response Export separate response partial success accepted spans rejected spans retryable failure responses apply to one hop
OTLP exports telemetry and returns a response on each adjacent hop. The illustrative partial-success batch has three accepted spans and one rejected span; it should not be retried wholesale as though nothing was accepted. A collector response does not prove final backend storage.

View in the full Protocols collection