OpenTelemetry
OpenTelemetry is a CNCF standard for generating, collecting and exporting traces, metrics and logs from your services using one vendor neutral set of APIs and SDKs, so you can switch observability backends without rewriting instrumentation code.
Why it exists
Before OpenTelemetry, instrumenting an application meant picking a vendor's proprietary agent or SDK, so switching observability tools later meant re-instrumenting every service. Two competing open standards, OpenTracing and OpenCensus, tried to fix this separately and ended up splitting the ecosystem further. OpenTelemetry exists because the CNCF merged both efforts into one project, giving the industry a single vendor neutral way to instrument code once and export the data anywhere.
The mental model
Think of OpenTelemetry as a universal power adapter for telemetry. Your application generates traces, metrics and logs in one standard plug shape, the OTLP protocol, and the Collector is the adapter box that can route that same plug into whatever regional socket you have, Prometheus, Jaeger, Grafana, or a commercial vendor, without you rewiring the appliance itself.
How it works
An application links an OpenTelemetry SDK for its language, which wraps or auto instruments frameworks, HTTP clients and database drivers to emit spans for traces, data points for metrics and structured logs, each tagged with resource attributes like service name and pod name. That data is typically sent over OTLP to an OpenTelemetry Collector, a standalone process or Kubernetes sidecar or daemonset that receives telemetry, applies processors like batching, sampling and PII scrubbing, then exports it to one or more backends through pluggable exporters. Context propagation headers travel with requests across service boundaries so a single trace can span many microservices.
When it matters
It matters most in Kubernetes environments with many microservices, where without distributed tracing a slow request is nearly impossible to debug because you cannot see which of ten downstream calls caused the latency. The common footgun is treating instrumentation as free: unbounded cardinality in metric labels, unsampled traces at high volume, or a misconfigured Collector pipeline can quietly overwhelm both your telemetry backend and its bill.
A concrete example
A checkout service in a Kubernetes cluster calls inventory, payment and shipping services. With OpenTelemetry auto instrumentation and a Collector deployed as a daemonset, a single trace ID follows one checkout request through all four services, and an engineer debugging a timeout sees in one trace view that the payment service call alone took four of the request's five total seconds.
Interview question
What specific problem does the OpenTelemetry Collector solve that instrumenting each service directly with a vendor SDK does not?
- a.It makes traces and metrics free to store regardless of volume
- b.It replaces the need for structured logging inside application code
- c.It automatically fixes performance problems it detects in a service
- d.It decouples telemetry export from application code, so you can change or add backends through Collector configuration instead of redeploying every instrumented serviceCorrect
Why? this is the answer
The Collector receives vendor neutral OTLP data and routes it to whichever backend you configure, so switching or adding an observability tool is a config change rather than a re-instrumentation project. It has no effect on storage cost, cannot fix bugs itself, and does not remove the need for services to still emit their own logs.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #opentelemetry
- #cncf
- #insufficient source
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on opentelemetry — each one lists the topics its interview covers.
See open roles