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.

What the interviewer is probing.

What the interviewer is probing.

1. "What is OpenTelemetry trying to solve?" *Probing:* the purpose. *Stalls:* "Tracing." *Moves up:* vendor-neutral instrumentation — you instrument once and change backend without re-instrumenting the estate.

1. "What is OpenTelemetry trying to solve?"

2. "What are the signals?" *Probing:* the breadth. *Stalls:* "Traces." *Moves up:* traces, metrics and logs, with profiling newer — all sharing one context and resource model.

2. "What are the signals?"

3. "What are semantic conventions and why do they matter?" *Probing:* the underrated part. *Stalls:* "Naming." *Moves up:* agreed attribute names, so a dashboard built on http.request.method works across services and languages without mapping.

3. "What are semantic conventions and why do they matter?"

4. "What is the maturity caveat?" *Probing:* honesty. *Stalls:* "It is all stable." *Moves up:* tracing is stable, metrics largely so, logs the least mature — worth knowing before promising a full migration.

4. "What is the maturity caveat?"