Explain The Standard — Signals & Semantics in Observability

1 / 4

OpenTelemetry

The Standard — Signals & Semantics

Understand OpenTelemetry as a vendor-neutral standard for metrics, logs, and traces.

OpenTelemetry (OTel) is not a backend — it is an open standard and a set of tools for generating, collecting, and exporting telemetry, governed by the CNCF. Its goal is to decouple instrumentation from any particular vendor: you instrument once with OTel, then point the data at Datadog, New Relic, Grafana, Elastic, or anything else, without changing application code. It is the merger of the earlier OpenTracing and OpenCensus projects and has become the industry-standard instrumentation layer.

A universal power standard like USB-C: devices and chargers from any brand interoperate because they agree on the connector and protocol — you are no longer tied to one manufacturer's cable.

Key Concepts

OTel defines three signals — traces, metrics, and logs — plus baggage for propagating context. Crucially, it also defines semantic conventions: agreed-upon names for common attributes (http.request.method, db.system, service.name) so data is consistent regardless of language or vendor. The wire format is OTLP (OpenTelemetry Protocol). For interviews, the key framing is: OTel standardises how telemetry is produced and shipped; the storage and analysis still belong to a backend.